Yep, Data::Dumper for example will complain (under -w) about printing to an unopened file handle if you say
Actually its perl that complains here. The warning is provided because perl reads
print Dumper $quux;
as
use IO::File;
Dumper->print($quux);
when 'Dumper' is an unknown bareword. Personally I always disambiguate print statements in some way just because ive been bitten a few times.
Incidentally in this case its not much harder (and often desirable) to replace that with
print Data::Dumper->new([$quux],['quux'])->Dump(),"\n";
I say desirable, and use the long winded ->new() form because now we can easily add stuff in the middle:
# we have large cyclic structures: disable pretty indent, enable purit
+y mode.
print Data::Dumper->new([$quux],['quux'])->Purity(1)->Indent(1)->Dump(
+),"\n";
---
demerphq
<Elian> And I do take a kind of perverse pleasure in having an OO assembly language...
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:
- 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
Outside of code tags, you may need to use entities for some characters:
| |
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.
|
|