Re: bug in optional argument processing (?)

On Fri, 24 Mar 2006, Leon Bottou wrote:

> I simply did not want to introduce another source of dependencies
> between the behavior of a function and the dynamical calling context.

I'm not really happy with the CL behavior either. I think evaluation
once at time of definition makes most sense. That is,

(defparameter *global-val* 5)

(defun f (val &optional (other-val *global-val*))
   (+ val other-val))

(f 0) -> 5

(defparameter *global-val* 4711)

(f 0) -> 5


Isn't that the behavior most people would expect?

ralf



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642