Re: (nearly) readonly globals

Is there a bug? Are the docs ambiguous?

No. And No. Using local creates a temporary instance of the named variable, and you can do what you like with it.

That WAD (Working As Designed)

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

Comment on Re: (nearly) readonly globals

Replies are listed 'Best First'.
Re^2: (nearly) readonly globals by haoess (Curate) on Jan 19, 2009 at 20:32 UTC
Using local creates a temporary instance of the named variable, and you can do what you like with it. But this does not apply to all special globals, i.e.: `% perl -e 'local $1 = 1' Modification of a read-only value attempted at -e line 1. % perl -e 'local $^S = 1' Modification of a read-only value attempted at -e line 1.` [download] -- Frank	[reply] [d/l]
Re^3: (nearly) readonly globals by Corion (Patriarch) on Jan 19, 2009 at 20:35 UTC
Yes - see local, resp. the documentation referenced by it, Private Variables via my() in perlsub.	[reply]
Re^4: (nearly) readonly globals by haoess (Curate) on Jan 26, 2009 at 18:49 UTC
I don't give up: `% bleadperl -Mstrict -wE 'for $1 ( 10..13 ) { say $1 }' 10 11 12 13` [download] And now, these globals loose their magic: `% bleadperl -Mstrict -wE 'for $1 ( 10..13 ) { $1 =~ /^(\d)/; say $1 }' 10 11 12 13` [download] -- Frank	[reply] [d/l] [select]