<?xml version="1.0" encoding="windows-1252"?>
<node id="959180" title="Re^5: can't import using exporter" created="2012-03-12 17:10:29" updated="2012-03-12 17:10:29">
<type id="11">
note</type>
<author id="438862">
perl-diddler</author>
<data>
<field name="doctext">
Well first I got 
&lt;code&gt;
&gt; cnvWav2Flac
Undefined subroutine &amp;Debug::module_notational_filename called at /Audio/scripts/cnvWav2Flac line 85.
        Debug::BEGIN() called at /Audio/scripts/cnvWav2Flac line 85
        eval {...} called at /Audio/scripts/cnvWav2Flac line 85
BEGIN failed--compilation aborted at /Audio/scripts/cnvWav2Flac line 85.
&lt;/code&gt;
Then reading manpage, it appeared, I needed to specifically include it... however, in doing so:
&lt;code&gt;
&gt; cnvWav2Flac        
"module_notational_filename" is not exported by the Module::Runtime module
Can't continue after import errors at /usr/lib/perl5/site_perl/5.14.2/Module/Runtime.pm line 154.
        Module::Runtime::import('Module::Runtime', 'module_notational_filename') called at /Audio/scripts/cnvWav2Flac line 5
        main::BEGIN() called at /Audio/scripts/cnvWav2Flac line 5
        eval {...} called at /Audio/scripts/cnvWav2Flac line 5
BEGIN failed--compilation aborted at /Audio/scripts/cnvWav2Flac line 5.&gt; cnvWav2Flac        
"module_notational_filename" is not exported by the Module::Runtime module
Can't continue after import errors at /usr/lib/perl5/site_perl/5.14.2/Module/Runtime.pm line 154.
        Module::Runtime::import('Module::Runtime', 'module_notational_filename') called at /Audio/scripts/cnvWav2Flac line 5
        main::BEGIN() called at /Audio/scripts/cnvWav2Flac line 5
        eval {...} called at /Audio/scripts/cnvWav2Flac line 5
BEGIN failed--compilation aborted at /Audio/scripts/cnvWav2Flac line 5.
&lt;/code&gt;

I didn't have Module::Runtime, so it was just loaded and installed from CPAN.   Am I doing something wrong, or is this a bug in the module meant to work around various bugs?
&lt;p&gt;Reading the manpage, several bugs that I didn't know about, but that might explain why various programs have been breaking at each upgrade as things are 'fixed'... lexical leaks and such that I didn't know about might have caused things to work earlier, but cause failure once fixed.  
&lt;p&gt;Not sure -- speculation -- I have about 10 progs  or so, I've encountered so far that have stopped working as I upgraded from 5.10-&gt;12-&gt;14, actually 1 of those broke from 5.8-&gt;5.9, but given the fast pace of updates, I didn't get 12 installed until 14 was out.  So I have several programs that are broken now, and are on a 'to be looked at' queue, as time allows competing with current priorities....*sigh*..







</field>
<field name="root_node">
959066</field>
<field name="parent_node">
959155</field>
</data>
</node>
