Front page | perl.perl5.porters |
Postings from May 2003
This really isn't resolved, as
perldoc -f require states
If EXPR is a bareword, the require assumes a ".pm"
extension and replaces "::" with "/" in the
filename for you, to make it easy to load standard
modules. This form of loading of modules does not
risk altering your namespace.
but it doesn't mention .pmc.
If an appropriate file with a .pmc extension exists
(and is newer than a similar .pm file, or no .pm file is
found) perl will load the .pmc file.
This behavior is not documented in perldoc -f require.
dd:tmp$ cat Echo.pm
warn "Hello World\n";
dd:tmp$ cat Echox.pm
warn "Goodbye World\n";
dd:tmp$ perlcc -B Echo.pm -o Echox.pmc
/usr/local/bin/perlcc: Will not create a shared library for bytecode
dd:tmp$ touch Echox.pm
dd:tmp$ perl -le 'require Echox'
Goodbye World
dd:tmp$ touch Echox.pmc
dd:tmp$ perl -le 'require Echox'
Hello World
Same perl code, different output, based on timestamps of .pm and .pmc files!
On Fri, 9 May 2003 at 15:47 -0000, Casey West via RT <perlbug-followup@perl...:
> From: Casey West via RT <perlbug-followup@perl.org>
> To: dcd
> Date: 9 May 2003 15:47:29 -0000
> Subject: [perl #8860] [RESOLVED] .pmc extension not documented in require
>
> According to our records, your request regarding
> ".pmc extension not documented in require"
> has been resolved.
>
> If you have any further questions or concerns on the above subject, please
> respond to this message.
>
> For other topics, please create a new ticket.
>
> Please don't feel obligated to say "Thanks" or "Kudos" or "I want to have your
> child" or "I owe you a beer" -- if you respond to this message it will reopen the
> ticket. If you must, please send email directly to the person who handled your
> ticket, and not to the tracking system.
>
> <URL: http://rt.perl.org/rt2/Ticket/Display.html?id=8860 >
>
Thread Next