Article View: comp.lang.logo
Article #67Dynamic scope (was Re: Future of Logo)
From: Alan J Rosenthal
Date: Thu, 06 Aug 1992 00:47
Date: Thu, 06 Aug 1992 00:47
13 lines
1137 bytes
1137 bytes
bh@anarres.CS.Berkeley.EDU (Brian Harvey) writes: >in Logo, lexical scope would just be a restriction. (That is, the variables >available to a given procedure under lexical scope would be a subset of the >variables available to it with dynamic scope.) I don't think that this is quite correct... if a name is the name both of a global variable and of a local variable in an enclosing procedure frame, then with dynamic scope you get the variable in the enclosing procedure frame, but with lexical scope you get the global variable. Neither of these sets is a subset of the other. (But I definitely share your affection for dynamic scoping, at least in an interpreted language in which there's no penalty for it.)
Technical Details
Message-ID:
<1992Aug5.204731.22492@jarvis.csri.toronto.edu>Path:
arc1-ca.pugleaf.net!sparky!uunet!usc!rpi!utcsri!dgp.toronto.edu!flapsReferences:
<40716@skye.dcs.ed.ac.uk> <1992Aug5.100121.28641@beaver.cs.washington.edu> <15omhaINNgvr@agate.berkeley.edu>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!usc!rpi!utcsri!dgp.toronto.edu!flaps Newsgroups: comp.lang.logo From: flaps@dgp.toronto.edu (Alan J Rosenthal) Subject: Dynamic scope (was Re: Future of Logo) Message-ID: <1992Aug5.204731.22492@jarvis.csri.toronto.edu> References: <40716@skye.dcs.ed.ac.uk> <1992Aug5.100121.28641@beaver.cs.washington.edu> <15omhaINNgvr@agate.berkeley.edu> Date: 6 Aug 92 00:47:31 GMT Lines: 13