On Tue, 8 Apr 2003, Lawrence Greenfield wrote:
does require carry over? I'd say "no". variables shouldn't either.
It's not clear to me. Nor is it clear that sites won't want to have
variables cascade.
Currently Cyrus's include draft has require being scoped to the current
script. I think this is fine for features that only enable certain forms
of syntax (since they basically dissapear at parsing time), but is
somewhat less good for things that change global state of the interpreter.
Implicit keep is another "global state" issue that jumps to mind.
I think I'm currently of the opinion that all global state
(including variables, implicit keep, etc) should be global for the entire
execution. However, the effects of require which only affect parsing
should be limited to the current script only.
I do think Larry is correct that there are many cases that will be hard to
understand without formal syntax.
-Rob
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Rob Siemborski | Andrew Systems Group * Research Systems Programmer
PGP:0x5CE32FCC | Cyert Hall 207 * rjs3(_at_)andrew(_dot_)cmu(_dot_)edu *
412.268.7456
-----BEGIN GEEK CODE BLOCK----
Version: 3.12
GCS/IT/CM/PA d- s+: a-- C++++$ ULS++++$ P+++$ L+++(++++) E W+ N o? K-
w O- M-- V-- PS+ PE++ Y+ PGP+ t+@ 5+++ R@ tv-@ b+ DI+++ G e h r- y?
------END GEEK CODE BLOCK-----