|XP is just a number|
Re^5: How will you use state declared variables in Perl6?by BrowserUk (Pope)
|on Jul 08, 2005 at 22:29 UTC||Need Help??|
I'm still not seeing a difference in safety.
If Limbic~Region's analogy with C statics is accurate, state defines an single, absolute, static piece of ram. So, this:
are semantically quite different.
In the former case, each time you generate a coderef by calling genclosure(), that coderef will close over a different instance of the lexical $bar.
In the latter case, each coderef generated will reference the same, single, immovable, static piece of ram</code> labelled $bar.
And further, references to state $bar; in other unrelated generator functions--in the same package, or a different packages, or a different modules--will all refer to that same static piece of ram.
It is possible that state will be cleverer than that, and somehow be scoped by file or package or namespace, but then a) the analogy with C static falls through; b) the would seem to be considerable overlap with local $bar;.
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
Lingua non convalesco, consenesco et abolesco. -- Rule 1 has a caveat! -- Who broke the cabal?
"Science is about questioning the status quo. Questioning authority".
The "good enough" maybe good enough for the now, and perfection maybe unobtainable, but that should not preclude us from striving for perfection, when time, circumstance or desire allow.