My preference is not widely shared. I take a page
from Linus Torvalds, define the API to program to, and
write a simple wrapper for that API. Then all I ever
need to do is write to that wrapper.
I might implement in this case by checking for the existence of
the module at run-time, and initialize a bunch of anon
subs accordingly. My API wind up behind the scene
calling them, and they will automagically do the right
thing (even if that thing is to spit out debugging info
or else just do nothing).
For the full philosophy, here is a good rant from Linus explaining
the why's and wherefore's. Even if you disagree it is a
worthwhile read.
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.