Given what .pmc is for, I'd say reporting it on the .pm is correct. If you're abusing the mechanism, you get abusive error messages in return.
Even in original intent of .pmc, both in the .pm and in the .pmc, (different) things can go wrong. And they should be reported from the right file. Especially reporting an error in a file that doesn't exist is a bit silly.
For example, with the original Bytecode/Byteloader stuff, the PMC loads Byteloader with a version check. If that version check fails, the error is reported from the PM, which has nothing to do with the error. That makes debugging hard. Hiding the fact that there's another file involved, is bad.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|