Extraordinary!!
> x.pl
"module_notational_filename" is not exported by the Module::Runtime mo
+dule
Can't continue after import errors at ./x.pl line 4.
BEGIN failed--compilation aborted at ./x.pl line 4.
Ishtar:/Audio/scripts> ^C
Ishtar:/Audio/scripts> cat x.pl
#!/usr/bin/perl -w
use strict;
use Module::Runtime qw(module_notational_filename);
<p>
<p>
You can't say I didn't pare down my test program... right?
It's does have some fluff. a blank line. sorry, I'm just lazy.
<p>
<p>
Maybe you can get off your extraordinary high horse and realize that s
+imple usage as documented in the manpage isn't tested in the CPAN Mat
+rix, because I've given you extraordinary evidence that functionality
+ in that module is broken and Guess what -- that KEYWORD is in
a @EXPORT_OK line -- so the evidence just rose extraordinarily that so
+mething broke in 6.5.14 that this module relied on -- that has now ch
+anged.
<p>
Are you still in denial or how many modules do I have to find I had an
+other program that worked fine in 6.5.12, -- fails to work now with s
+imilar errors as the one above.
<code>
Useless use of multiplication (*) in void context at /home/law/bin/ded
+up line 664.
String found where operator expected at /home/law/bin/dedup line 762,
+near "Warn "Cannot cache scan results in %s: %s\n""
(Do you need to predeclare Warn?)
String found where operator expected at /home/law/bin/dedup line 776,
+near "Error "No Cached scan file in $scan_res_path to use.\n""
(Do you need to predeclare Error?)
String found where operator expected at /home/law/bin/dedup line 780,
+near "Warn "Ignoring cached results file '$scan_res_path'.\n""
(Do you need to predeclare Warn?)
String found where operator expected at /home/law/bin/dedup line 787,
+near "Warn "Cannot cache scan results in %s: %s\n""
(Do you need to predeclare Warn?)
String found where operator expected at /home/law/bin/dedup line 820,
+near "Error "FATAL: Starting paths must be on same device.\n""
(Do you need to predeclare Error?)
String found where operator expected at /home/law/bin/dedup line 827,
+near "Warn "$_: neither file nor dir. Ignoring in scan.\n""
(Do you need to predeclare Warn?)
String found where operator expected at /home/law/bin/dedup line 833,
+near "Error "$_ not readable; pathname blocking further examination\n
+""
(Do you need to predeclare Error?)
String found where operator expected at /home/law/bin/dedup line 849,
+near "Debug "Got %d paths from command line\n""
(Do you need to predeclare Debug?)
String found where operator expected at /home/law/bin/dedup line 862,
+near "safe_printf "debug=%s, verbose=%s, scandev=%04x; ""
(Do you need to predeclare safe_printf?)
syntax error at /home/law/bin/dedup line 743, near "confess sprintf"
syntax error at /home/law/bin/dedup line 762, near "Warn "Cannot cache
+ scan results in %s: %s\n""
syntax error at /home/law/bin/dedup line 776, near "Error "No Cached s
+can file in $scan_res_path to use.\n""
syntax error at /home/law/bin/dedup line 780, near "Warn "Ignoring cac
+hed results file '$scan_res_path'.\n""
syntax error at /home/law/bin/dedup line 787, near "Warn "Cannot cache
+ scan results in %s: %s\n""
syntax error at /home/law/bin/dedup line 820, near "Error "FATAL: Star
+ting paths must be on same device.\n""
syntax error at /home/law/bin/dedup line 827, near "Warn "$_: neither
+file nor dir. Ignoring in scan.\n""
syntax error at /home/law/bin/dedup line 833, near "Error "$_ not read
+able; pathname blocking further examination\n""
syntax error at
It's like stops exporting things reliably in larger, non-trivial programs.
But of course trivial ones still work, so people can prove it works... *BROKEN*
-
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.