> > What about if the symbol doesn't exist in the caller's scope > > and the caller is not in the process of being compiled? Can > > the new symbol be ignored since there obviously isn't any > > code in the caller's scope referring to a lexical with that > > name? > > No. Because some other subroutine called from the caller's scope might > also access caller().{MY}. In fact, you just invented a new pattern, in > which a set of subroutines called within a scope can communicate invisibly > but safely through that scope's lexical symbol table. Foxy variables. Nice.
- Re: What's up with %MY? Damian Conway
- Re: What's up with %MY? Dan Sugalski
- Re: What's up with %MY? Ken Fox
- Re: What's up with %MY? Damian Conway
- Re: What's up with %MY? Uri Guttman
- RE: What's up with %MY? Garrett Goebel
- Re: What's up with %MY? Dave Mitchell
- RE: What's up with %MY? Garrett Goebel
- RE: What's up with %MY? Dan Sugalski
- Re: What's up with %MY? Damian Conway
- Re: What's up with %MY? Me
- Re: What's up with %MY? Ken Fox
- Re: What's up with %MY? Uri Guttman
- Re: What's up with %MY? Dan Sugalski
- Re: What's up with %MY? Damian Conway
- RE: What's up with %MY? Damian Conway
- RE: What's up with %MY? Dan Sugalski
- Re: What's up with %MY? Bryan C . Warnock
- RE: What's up with %MY? Damian Conway
- Re: What's up with %MY? Damian Conway
- Re: What's up with %MY? Dan Sugalski