From: Dave Mitchell [mailto:[EMAIL PROTECTED]] > "Bryan C. Warnock" <[EMAIL PROTECTED]> mused: > > Consider it like, oh, PATH and executables: > > `perl` will search PATH and execute the first perl > > found, but 'rm perl' will not. It would only remove > > a perl in my current scope..., er, directory. > > But surely %MY:: allows you to access/manipulate > variables that are in scope, not just variables are > defined in the current scope, ie > > my $x = 100; > { > print $MY::{'$x'}; > } > > I would expect that to print 100, not 'undef'. Are your > expectations different? Hmm, shouldn't that print something like SCALAR(0x1b9289c)? If you meant ${$MY::{'$x'}} then I'd agree...
- RE: What's up with %MY? Dave Mitchell
- Re: What's up with %MY? Ken Fox
- RE: What's up with %MY? Dave Mitchell
- Re: What's up with %MY? David L. Nicol
- Re: What's up with %MY? Bryan C . Warnock
- Re: What's up with %MY? Bryan C . Warnock
- Re: What's up with %MY? Bart Lateur
- Re: What's up with %MY? Dave Mitchell
- Re: What's up with %MY? Bryan C . Warnock
- 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? Ken Fox
- Re: What's up with %MY? Uri Guttman
- Re: What's up with %MY? Dan Sugalski
- Re: What's up with %MY? Dan Sugalski
- Re: What's up with %MY? Ken Fox
- Re: What's up with %MY? Dan Sugalski
- RE: What's up with %MY? Garrett Goebel
- Re: What's up with %MY? Ken Fox
- Re: What's up with %MY? Dan Sugalski