Re: Re^6: Lexical pad / attribute confusion

Which brings this doozie that I previously struggled with. Why can't peeker see @bar ?

use warnings;
use strict;

INIT {
   use Data::Dumper;
   use PadWalker qw (peek_my peek_sub);    
   print Dumper(peek_my(1));
}

my $foo = 'lee';
my $bar = "Bar";

sub peeker{
    print Dumper(peek_my(shift));
}
print Dumper(peek_my(0));

{ my @foo = (1..3) }
{ 
  my @bar = (9..12);
  peeker(1);

}
print Dumper(peek_my(0));
__END__
$VAR1 = {
          '$foo' => \undef,
          '@foo' => [],
          '$bar' => \undef,
          '@bar' => []
        };
$VAR1 = {
          '$foo' => \'lee',
          '$bar' => \'Bar'
        };
$VAR1 = {
          '$foo' => \'lee',
          '$bar' => \'Bar'
        };
$VAR1 = {
          '$foo' => \'lee',
          '$bar' => \'Bar'
        };
[download]

I don't know enough to say for sure, but when INIT is called, the pad accesses are probably all figured out. Then after INIT, it does whatever magic it does to give the appearence of a scope to a bare block. I would think that even though they are unavailable to the outer scope, their position is retained in the pad list. Otherwise the location of a my var would change from before and after the bare block.

-Lee

"To be civilized is to deny one's nature."

Comment on Re: Re^6: Lexical pad / attribute confusion Download Code

Replies are listed 'Best First'.
Re^8: Lexical pad / attribute confusion by adrianh (Chancellor) on Dec 22, 2002 at 11:26 UTC
Which brings this doozie that I previously struggled with. Why can't peeker see @bar ? Running perl 5.8 and PadWalker 0.08 you do! `$VAR1 = { '$foo' => \undef, '@bar' => [], '@foo' => [], '$bar' => \undef }; $VAR1 = { '$foo' => \'lee', '$bar' => \'Bar' }; $VAR1 = { '$foo' => \'lee', '@bar' => [ 9, 10, 11, 12 ], '$bar' => \'Bar' }; $VAR1 = { '$foo' => \'lee', '$bar' => \'Bar' };` [download] Are you using the same version of PadWalker?	[reply] [d/l]
Re: Re: Re: Re^6: Lexical pad / attribute confusion by shotgunefx (Parson) on Dec 22, 2002 at 21:18 UTC
You are correct, it's been fixed. Using 5.6 with PadWalker 0.8 on my 'nix box it works fine. Previously it did not. (The script I originally tested the code for this post on was 5.6.1 Win32 with PadWalker 0.5) -Lee "To be civilized is to deny one's nature."	[reply]