Excellent review of scoping, arturo. The only nit that I have with the writeup is that you leave some of the more important results of print results out (for example, in the very last example, what does the last print statement in the main body of the problem put out?). Certainly, one can copy and paste the code into perl and see what comes out, bu it might be better to make sure to include the unmodified output for each little script right after the script, making sure that each printed line can be unambigously traced back into the program.
But kudos on covering a difficult subject and getting across the difference between my and local, something I've always had trouble with!
Update: Arturo did the corrections as indicated, so this is most redundant, but this comment should still serve to remind future writers to include all output particularly if it's necessary for program understading :).
Dr. Michael K. Neylon - email@example.com
"You've left the lens cap of your mind on again, Pinky" - The Brain
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:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- 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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||