Personally, I'm inclined to call it a bug, as it violates the principle of least surprise - behaving differently based on the order in which subs are defined is a very surprising behaviour. I consider inconsistencies to be a category of bug, so those two options are equivalent, IMO. And I can't imagine how it could possibly qualify as a feature, so "bug" is really the only option left.
However, I consider it to be a bug in the code which reuses the name much more so than a bug in perl itself. It's an excellent example of why one should follow the standard Perl convention of using InitialCaps for module names and all_lowercase for sub names, or at least follow some convention which distinguishes the two types of names. If a programmer chooses to name things ambiguously and gets bitten by that ambiguity, I'd say he deserves the pain that results. Unfortunately, that pain is more often felt by an innocent maintenance programmer rather than by the one who caused the problem in the first place.
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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||