This can’t be emphasized enough. A couple of years ago I was wrestling with a really old application which “inexplicably” did not run on one of several different machines. It turned out to be a problem such as this: there was a common subroutine-name, more than one potential source of it, and a very slight difference in the file setup on that one machine ... a file was there but not being picked up, long story. But the bottom line was that the intended (correct ...) behavior of that code as-written was in effect contextually determined, with an ambiguity in play that was hiding the root problem. Learning from this, I now try to be as explicit as possible in every place where such ambiguities might occur: using qw() import-lists with large “kitchen sink” utility packages, and sometimes empty lists there with explicit fully-qualified (i.e. with package name expressly specified) references to the exact routine that I need. These problems, when I have seen them, come from software that was originally written for older Perls.
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:
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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||