From what I recall, Perl 6 will have similar concepts of piping. The difference, however, is that perl 6 gets the advantage of being able to define brand new operators, while the developer(s) of FEAR::API or even IO::All can't. (They would be able to define new operators in perl 6 - but now we're getting ahead of ourselves.) Thus, someone with some clout in the design of perl 6 has decided that this type of development is a Good Thing (tm) - both the piping and the ability to define new operators that the designers of the language didn't anticipate. I don't disagree - coming from some experience with C++'s IO streams, I thought they were clever overloads that had the advantage of becoming standard and thus not funny looking (anyone who had C++ experience would be expected to be familiar with them), and where they used >> and << only because they couldn't create a new operator (and then it was stuck before a new operator could be defined).

However, this is not standard in perl 5. For that reason alone, I would discourage it in anything approaching production (and thus maintainable) code. I would suggest your last example, the "full OO" one, to be the best use of Perl 5 as Perl 5.

In reply to Re: Overload abuse or is it just me? by Tanktalus
in thread Overload abuse or is it just me? by salvix

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.