I will agree that IO::All (with it's use of Spiffy) makes for some clean looking code. However, IO::All is just crammed with everything and the kitchen sink thrown into one module, and even a way to further extend it with plugins!

Spiffy itself is somewhat questionable in my mind as well since it does so many different things in one module. But after seeing how quickly ingy can whip out new Spiffy based modules, I am less bothered by that fact (usefulness almost always outweighs overly-anal-elegance).

Back to IO::All, I do have to say that it is very nice when you are writing quick scripts and tools. It takes the headache out of doing some very complex stuff when you just don't have the time to do it the "right" way (the "right" way being a subjective thing). But to use it for any serious sizable project IMO would be inadvisable.

But of course, this does not mean it is not good code to read :), in fact I rather enjoyed reading it (and learned plenty about obscure IO techniques as well). I would also recommend a look at Spiffy too, it has some rather interesting code in it as well.

-stvn

In reply to Re^2: What CPAN modules are "good reads"? by stvn
in thread What CPAN modules are "good reads"? by tlm

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.