To be perfectly honest, my first thought when I saw
IO::All is that it is a solution in search of a
problem. Maybe I'm just missing something, but it
seems rather pointless to me, a needless exercise in
wheel-reinventing on a grandscale with no benefit.
Maybe this is because I'm comfortable with the way
Perl does IO already, for the most part, or maybe I
just don't think the same way as the guy who did
IO::All, but in any case I just don't see the value.
Regarding API design, I agree with EvdB's
comment,
"Can I remember how to use this
after a week and in a hurry without the docs?".
My favourite example of a module that gets this
pretty-much right, IMO, is DateTime,
which I can almost use in my sleep. (There are
some modules that are even easier to remember how
to use, such as Data::Dumper, but
what DateTime does is sufficiently complex
that one might expect a more difficult API.
;$;=sub{$/};@;=map{my($a,$b)=($_,$;);$;=sub{$a.$b->()}}
split//,".rekcah lreP rehtona tsuJ";$\=$;[-1]->();print
-
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.
|
