This is interesting, since I've noticed a lot of people grumbling about this with modules that require globs (one of mine included). The true wizards can always overload a filehandle, using Tie::Handle if necessary. But what I was wondering is if anyone thinks it'd be worthwhile for me (or someone else, I suppose) to whip up a module to wrap up all of this overloading stuff into one convenient package. Say....Tie::UniversalHandle or something. So you could just do: tie *FH, Tie::UniversalHandle, $some_string; or tie *FH, Tie::UniversalHandle, @some_array; and have all of the magic immediately wrapped up insde of the module. It'd spare people the trouble of having to roll their own module every time.

In reply to RE: pointing a filehandle at a scalar or array ? by jimt
in thread pointing a filehandle at a scalar or array ? by lindex

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.