I can agree to that. It really depends if it's mostly an internal process streamlined for fast development (often enough i only have hours to days to come up with a large one-off solution that's running for a limited time and scope). Or if the module is designed for a broad audience.

What it comes down to, in my mind at least, is that many of those problems could be avoided by an enhanced, clearer syntax for conditionally specifying modules as optional requirements ("i need that or that, but at least one of them") as well as clearer syntax for conditionaly using them in the scripts (best solution would be "try this list of modules in the given order and load the first one you find and tell me which one it was").

Example: Let's say we have two modules with the same API, but one for Linux/Unix and one for windows, i could them do 

my $pwmodule = use_first qw[Linux::Power Win32::Power];
my $power = $pwmodule::new();
$power->suspend();

[download]

"You have reached the Monastery. All our helpdesk monks are busy at the moment. Please press "1" to instantly donate 10 currency units for a good cause or press "2" to hang up. Or you can dial "12" to get connected directly to second level support."

In reply to Re^6: Building Win32::GuiTest for perl 5.14 or higher (Bad tests!) by cavac
in thread Building Win32::GuiTest for perl 5.14 or higher by SuicideJunkie

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.