Warn tells you not only the origin of the exception but also the the coordinates of the input you are reading.
Closing DATA might help, but I'm not sure about side effects, because it's the handle from which the compiler read the source code.
(If you seek DATA to 0 you can read your source again)
Furthermore does every file have its own DATA section, so I'd expect this to be gone if it happens in a module. Hm ... OTOH is possible to deduce the file from the first coordinates.
Anyway, I wouldn't care much about this, because a module shouldn't throw warnings in normal conditions or risk confusing the user anyway.
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.