Re: Dynamic scoping
- To: mathgroup at smc.vnet.net
- Subject: [mg129706] Re: Dynamic scoping
- From: Daniel Huber <danielphuber at gmail.com>
- Date: Wed, 6 Feb 2013 01:51:22 -0500 (EST)
- Delivered-to: l-mathgroup@mail-archive0.wolfram.com
- Delivered-to: l-mathgroup@wolfram.com
- Delivered-to: mathgroup-newout@smc.vnet.net
- Delivered-to: mathgroup-newsend@smc.vnet.net
- References: <keiatl$qq3$1@smc.vnet.net>
On Saturday, February 2, 2013 7:15:17 AM UTC+1, Daniel Huber wrote: > Block is supposed to be a dynamic scoping construct. Therefore, in the following, "Print" should be an undefined function. But consider: OOOPS, there was a typo, it should read: "Plus" should be an undefined function." not Print of course. One more thing, "dynamic scoping" is well defined, it means: the value of a variable is temporariliy stored away and set to undefined until the current scope is left. This is although true for all calls made from the current scope. Therefore, the above behaviour is a BUG! cheers, Daniel