Re^4: closure clarity, please

Ok, I can understand that confusion. Lexicals are actually allocated very early on (compile-time?) and on scope exit. This allows for the creation of private variables:

package Foo;

my $x;

sub set_x { validate($_[0]); $x = $_[0]; }
sub get_x { die("uninitialized") if !defined($x); $x }

1;
[download]

{
    my $x;
    sub set_x { validate($_[0]); $x = $_[0]; }
    sub get_x { die("uninitialized") if !defined($x); $x }
}
[download]

Comment on Re^4: closure clarity, please Select or Download Code

Replies are listed 'Best First'.
Re^5: closure clarity, please by JadeNB (Chaplain) on Nov 25, 2009 at 07:05 UTC
Lexicals are actually allocated very early on (compile-time?) I think that it must be true that lexicals are allocated at compile time—at least, if my timeline in Re^4: closure clarity, please is anything near the correct one. I can't see any other reason why the call to `f` on line 27 of Re^3: closure clarity, please (which I called step 9) would be affected by the call to `g` on line 23 (which I called step 7). (In fact, I thought that I stole this observation from a post of yours that I read long ago ….)	[reply] [d/l] [select]
Re^6: closure clarity, please by ikegami (Patriarch) on Nov 25, 2009 at 07:09 UTC
The alternative is that they could be vivified by the capture.	[reply]