comment on

Thank you, very much for the second link.

What is weird is that if my dbLoader writes the source to a file then returns a filehandle (the method used in the test) to that file both 'works.pl' and 'worksnot.pl' run successfully. But if dbLoader opens a filehandle on the reference to a string (aka in-memory-file) only 'works.pl' runs successful. 'worksnot.pl' still throws the error shown in the op.

Apparently I'm looking in the wrong place for the source of the problem. If dbloader opens a filehandle on an in-memory file where the contents are copied (rather than on the reference returned by the database) all is well. ie:

Won't work

        open my $fh,'<',$body_sref
            or die "Couldn't open '\$body_ref' for reading. $!";
        return $fh;
[download]

Will work

        open my $fh,'<',\(my $buffer=$$body_sref)
            or die "Couldn't open in-memory file for io. $!";
        return $fh;
[download]

In reply to Re^2: Coderefs and @INC (return filehandle or undef) by clueless newbie
in thread Coderefs and @INC by clueless newbie

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.


Perl Monk, Perl Meditation
	PerlMonks