comment on

Sometimes code involving IO handles can be confusing – that is because IO handles are of many kinds in Perl, like globs (the old way), glob refs, IO handles in scalar variables (produced with open and other IO operations), and legit objects which derive from IO::Handle, IO::File, etc.

The code in Email::Sender::Transport::Print wants an IO::Handle, or something that satisfies

$fh->isa('IO::Handle')

This is far from ideal – something more TIMTOWTDI, would be a check like the one of Scalar::Util::openhandle()

As you discovered, $fh is a glob ref, and does not satisfy this precondition. But that does

*{$fh}{IO}->isa('IO::Handle')

This fact is kind of sparse in perl documentation. For example, you can read that suggested at item 7 at Making References

You may use it in your code right now and / or submit a patch to Email::Sender::Transport::Print maintainer.

In reply to Re: Almost certainly a module documentation issue by ferreira
in thread Almost certainly a module documentation issue by dd-b

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.


laziness, impatience, and hubris
	PerlMonks