Unintended side effects are unintended side effects... The problem has nothing to do with aliasing and everything to do with not localising!
But surely the soul of wisdom is to avoid unintended consequences.
With paranoia, one can only hope to avert bad consequences; with knowledge one can know you have.
Don't hope, know!
Again, this is utterly without consideration of effects on performance, but in general, shouldn't one prefer the avoidance of a coding technique that depends on local-izing everything in sight in favor of one that takes advantage of the lexical scope associated with every subroutine definition by using only lexical variables? By so doing, one may know one has averted bad consequences – at least outside the lexical scope of the subroutine one is examining at the moment. (BTW: Is it possible to define a subroutine without creating a unique lexical scope for it? Offhand, I can't see a way.)
Oh well... Perhaps not even USD0.02-worth on this one. Anyway, I have to go shovel some snow now.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||