Often you want two APIs, a comprehensive and flexible one,
and an idiomatic DWIM wrapper Blah::Simple.
One way to reality check your design decisions is to
compare your API to another API from a different but
Another test (that I need) is to return to your
design after some months.
"What was I thinking?!" is often the result
when you lose the blinkers of your original problem.
I don't like API designs that second guess you,
nor those that strictly follow a non-Perlish design
(usually found in library or system wrappers)
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||