Re^2: initialise state variable from list context, NOT!

Thanks for the quick answer. The reason I thought I may get it to work with some hints for the compiler is that this is allowed

state %record;

%record = (
    getting => 'url',
    url     => 'http://',
    match   => '',
    getting => '',
    alarm   => 'no',
);
[download]

Is an empty hash considered as a safe case? Where is the border of what I can get away with?

Cheers,
R.

Pereant, qui ante nos nostra dixerunt!

Comment on Re^2: initialise state variable from list context, NOT! Download Code

Replies are listed 'Best First'.
Re^3: initialise state variable from list context, NOT! by JavaFan (Canon) on Sep 08, 2009 at 16:21 UTC
One of border cases is: `sub foo { (my $foo, state $bar) = (f(), g()); ... } foo; foo; # Should g() be called?` [download] As for `state %record;`, that is allowed. It's `state` in a list assignment that is disallowed. But note that `state %record; %record = ( ... );` [download] doesn't give you any benefits over `my %record = ( ... );` [download] You will have to write it as `state %record; %record = ( ... ) unless keys %record;` [download]	[reply] [d/l] [select]

Replies are listed 'Best First'.

sub foo {
    (my $foo, state $bar) = (f(), g());
    ...
}

foo;
foo;  # Should g() be called?
[download]

state %record;

state

state %record;
%record = ( ... );
[download]

my %record = ( ... );
[download]

state %record;
%record = ( ... ) unless keys %record;
[download]