The saying goes "Theres more than one way to do it", not "Theres more than one way you need to accomodate it". ;-)
TIMTOWDI (as I understood it) refers to the core language, not general API design. I would reconsider your approach - you probably do not want or need the hassle of excessive error checking on parameters, a combinatorial explosion of edge cases to test for, laborious contradictory POD, maintaining obscure language features etc etc.
If people dont like your API, well they can wrap it in "The Way They Want to Do It". And do their own damn testing.
Make it useful and easy to grok. Keep it Simple, Stupid.
time was, I could move my arms like a bird and...
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.