Ladislav, I disagree. I don't think this is an adequate proof. (You didn't observe the scan happening, so it's a theory, not an observation.)
In my understanding, context evaluates its blk argument, and as it moves along from item to item, finds set-words and their values and adds them to the new object that it is creating. I would say the BLK argument is scanned for local words *as* it is being executed. Forgive me if I misunderstood. It's not terribly clear. Regarding your final statement at bottom, would you say that the following statements are true? 1) "BLK ... scanned for local words" -means-> "BLK is reduced" 2) "... executed" -means-> "made into an object" Anton. > Hi, > > I don't think, that the difference between CONTEXT and FUNC is as clear as > Holger states. First of all, I think, that it is a matter of preferences > (which may differ). To demonstrate, that the difference is really small, > let's have a look at the following code sample: > > blk: [change at blk 9 first [b:] a: 1 placeholder 2] > c: context blk > probe blk > probe c > > Here we see, that the BLK ends up being changed to: > > == [change at blk 9 first [b:] a: 1 b: 2] > > Which would yield a different result than > > make object! [ > a: 1 > ] > > when used as the BLK argument. My observation is, that the BLK argument is > scanned for local words *before* it is being executed. -- To unsubscribe from this list, please send an email to [EMAIL PROTECTED] with "unsubscribe" in the subject, without the quotes.
