Re: PMC (Perl Module Compiled) survey

This isn't covered by the scope of your email request, so I'll mention it here:

feather:~ 107:$ echo 'sub abc { }' > foo.pmc
feather:~ 108:$ perl -Mfoo -le1
foo.pm did not return a true value.
BEGIN failed--compilation aborted.
[download]

perl has incorrectly reported the name of the file as foo.pm, not foo.pmc.

Jeff japhy Pinyan, P.L., P.M., P.O.D, X.S.: Perl, regex, and perl hacker
How can we ever be the sold short or the cheated, we who for every service have long ago been overpaid? ~~ Meister Eckhart

Comment on Re: PMC (Perl Module Compiled) survey Download Code

Replies are listed 'Best First'.
Re^2: PMC (Perl Module Compiled) survey by merlyn (Sage) on Mar 12, 2006 at 19:18 UTC
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. -- Randal L. Schwartz, Perl hacker Be sure to read my standard disclaimer if this is a reply.	[reply]
Re^3: PMC (Perl Module Compiled) survey by Juerd (Abbot) on Mar 12, 2006 at 20:27 UTC
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. Juerd # { site => 'juerd.nl', plp_site => 'plp.juerd.nl', do_not_use => 'spamtrap' }	[reply]