Re^2: Lexical pad / attribute confusion

[adrianh]

Hmm. Okay. What Elian said makes sense, but it leads to a new question.

If %foo amd %bar are in the same pad, just finagled into different slots, why can't that last call to dump_lex see them?

[shotgunefx]

Because they are declared after dump_lex.

-Lee

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

[adrianh]

They're also declared after INIT, and you can see them from there ;-) Also, moving dump_lex after the declarations like this:

Read more... (1370 Bytes)

Still gives you this (under 5.8):

when init top-level pad is
    HASH(0x22e150) -> $%bar = \{};
    HASH(0xb5b50) -> $%foo = \{};

when setting Attr in Foo for HASH(0xb5b50) top-level pad is

when setting Attr in Bar for HASH(0x22e150) top-level pad is
    HASH(0x22e150) -> $%bar = \{};

when runtime top-level pad is

[shotgunefx]

Actually I get different results. On 5.6.1 (win32) lexicals declared after INIT are not visible from INIT.

#!/usr/bin/perl

use warnings;
use strict;

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

}

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


{
    my @foo = (1..3);
}

{
    my @bar = (9..12);
}

print Dumper(peek_my(0))
__END___
$VAR1 = {};
$VAR1 = {
          '$foo
          '$bar
        };

my has both runtime and compile time effects, I wouldn't be suprised if they are on the same pad, but are removed from the padlist when the block is exited.

-Lee

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