Re: initialise state variable from list context, NOT!

There's no point giving the compiler a clue, as the compiler already knows what you are trying to do. And it's currently forbidden. The reason is that there are too many corner cases to let 'state LIST' be something that is intuitive all the time.

state $scalar is all that is allowed. Perhaps the best you can do is:

state $record = empty_record;
[download]

Comment on Re: initialise state variable from list context, NOT! Select or Download Code

Replies are listed 'Best First'.
Re^2: initialise state variable from list context, NOT! by Random_Walk (Prior) on Sep 08, 2009 at 14:17 UTC
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!	[reply] [d/l]
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]