"Bryan C. Warnock" wrote: > Except that Perl 6 will have the ability to inject lexical variables in its > scope, and in any dynamic parent's scope. (It isn't clear whether that is > write-only access or not - which it probably should be for lexicals.) > > That, invariably, forces at least some run-time lookup by name, since the > lexicals aren't there at compile time for the early resolution. Please, please, please say that this is not like Tcl's upvar/uplevel stuff. I was imagining the "injection" to happen *only* at compile time when a "use" statement replaced the scope management object the compiler talks to. I *really* don't like the idea of a called sub modifying its' parent's scope at run time. This fundamentally breaks the feature of understanding code just by reading it. When I see a lexical, I want to trust the definition. - Ken
- RE: Should MY:: be a real symbol table? Brent Dax
- Re: Should MY:: be a real symbol table? Ken Fox
- Re: Should MY:: be a real symbol table? Dan Sugalski
- Re: Should MY:: be a real symbol table? Ken Fox
- Re: Should MY:: be a real symbol table? Bryan C . Warnock
- Re: Should MY:: be a real symbol table? Dan Sugalski
- RE: Should MY:: be a real symbol table? Brent Dax
- RE: Should MY:: be a real symbol table? Dan Sugalski
- Re: Should MY:: be a real symbol table? Ken Fox
- Re: Should MY:: be a real symbol table? Dan Sugalski
- Re: Should MY:: be a real symbol table? Ken Fox
- Re: Should MY:: be a real symbol table? Dan Sugalski
- Re: Should MY:: be a real symbol table? Nathan Torkington
- RE: Should MY:: be a real symbol table? Brent Dax
- Re: Should MY:: be a real symbol table? Bryan C . Warnock
- Re: Should MY:: be a real symbol table? Dan Sugalski
- RE: Should MY:: be a real symbol table? Dan Sugalski
- Re: Should MY:: be a real symbol table? Ken Fox
- Re: Should MY:: be a real symbol table? Dan Sugalski
- Re: Should MY:: be a real symbol table? Ken Fox
- Re: Should MY:: be a real symbol table? Dan Sugalski