You are right in correcting my statement with your clogging
logs point. I was trying to express that debugging code does
not follow the normal rules of proper/good/correct coding.
It is equally easy to imagine a name-conflict where you
mistakenly call a defined routine thinking you were AUTOLOADing
it. Then instrumenting your code the other way could be
more helpful.
Or that your other thirty thousand
AUTOLOAD calls result
in logging indirectly.
You gave me a laugh, thanks.
I don't believe you think that using caller to
implement access control or interface selection is a reasonable
idea. I don't believe that even though you just said it.
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.