"our" is one of the best improvements in perl, because one has not to fiddle around anymore with different scoping rules for "my" and "vars" and allows consistent declarations! That's orthogonality (almost) at it's best! Unfortunately the features are ignored by the wide public, thinking it's just a a new name for an old mechanism.
Anyway there are some traps when our is used with special vars, for instance
something like our $\="\n"; will make B::Deparse fail ...
lanx:~$ perl -MO=Deparse perl/myour.pl
While deparsing perl/myour.pl near line 3,
Unexpected our($\)
CHECK failed--call queue aborted.
lanx@:~$ perl -version
This is perl, v5.8.8 ...
nice for obfuscation ; )
> In any case this is an example of why it is better to have a precise understanding of how features work rather than having a vague impression that is going to mostly work, most of the time.
FULL ACK! Especially because really understanding "our" implies really understanding "my".
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.