Personally I would go for two files - then you can add a third when you support Mac, and a forth when you support Symbian, and so on. It is just easier to maintain. I don't know of another module on CPAN that does things like that, I use a condition use. Here are some examples:
use if ($^O eq "MSWin32"), 'Win32::Process';
use if ($^O eq "MSWin32"), 'Win32::SearchPath';
use if ($^O ne "MSWin32"), 'POSIX';
use if ($^O ne "MSWin32"), 'POSIX' => ':sys_wait_h';
# Hack to allow compilation under Unix
# (NORMAL_PRIORITY_CLASS and INFINITE are Win32 only)
use if ($^O ne "MSWin32"), 'constant' => 'NORMAL_PRIORITY_CLASS';
use if ($^O ne "MSWin32"), 'constant' => 'INFINITE';
Your idea of sub-modules under a "master" namespace seems reasonable to me.
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.