Just my 2 cents worth, WHY is setting words in functions to 'none by default useful?
Why is the ability to use apparently unset words a desirable feature? Does this not confuse the language in that words cannot be used until after they have been defined? Now we have another "exception" case for words in functions. What makes words in functions different from global words or words in objects or words in a use context? Why the special case? cheers, Mark Dickson In a message dated Tue, 4 Dec 2001 6:44:01 PM Eastern Standard Time, "Larry Palmiter" <[EMAIL PROTECTED]> writes: > Hi Romano, > > I think we are in good agreement on the mechanics. > > > This is the "strange" (but useful) thing which happens in function body > (and > > not in use or object body): at the start of the execution of function body > all > > the context values are set to none or to the value of args (true for > > refinement!). > > > > Another way of looking at this is to note that USE and MAKE OBJECT! both > result in immediate evaluation of their body (or spec) blocks, but for > functions the body is only evaluated when the function is applied. > > Ciao > -Larry > > > -- > To unsubscribe from this list, please send an email to > [EMAIL PROTECTED] with "unsubscribe" in the > subject, without the quotes. -- To unsubscribe from this list, please send an email to [EMAIL PROTECTED] with "unsubscribe" in the subject, without the quotes.
