but then what about globals? Should they always be aliased? ... And then what about $_ – do we leave it as a strange exception case?

$_ already is a "strange exception", it gets used without being mentioned and has a myriad of magical behaviours associated with it (that I wouldn't want to loose), this would continue the tradition of that variable.

In the case of other globals, I hadn't really thought about them much as I don't make use of them much, but having thought about it, I don't think that there is a case for localisation.

If they already exist in the symbol table, they have been used before, and should not be localised. The programmer has explicitly indicated that they wish to re-use this variable, and any changes should persist. Trust that the programmer knows what they are doing.

If the programmer wants to both re-use an earlier global, and retain it's original value afterward, he has the option to localise it himself--just as he would have to in any other situation.

If the variable does not yet exist in the symbol table, there is no great value in localising it, and you remove the potential for using it's final value subsequent to the loop.

So basically, $_ is special--because it is already special--and for any other variable, the user controls localisation through the keywords my or local, just as he would for any other construct.

Seems to me that would be the most logical, useful and consistant behaviour. Still, it's all academic anyway.

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".
In the absence of evidence, opinion is indistinguishable from prejudice.

In reply to Re^10: no chunk is too small by BrowserUk
in thread Last undefines a for loop's itererator? by BUU

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.