Well, that seems like an open door. But I disagree. Part of programming is finding a trade-off between conflicting goals. Portability is one goal. But readability is another - and not necessarely a less important goal than portability. For the majority of the code I write, if there are any portability issues they are whether they will work with a different version of the kernel, or different versions of other used tools.

The loss in readability between: 

    $file = "fnord/glop/bibba";

[download]
and 
    $file = File::Spec -> catfile (qw /fnord glop bibba/);

[download]
is significant. Enough for me to offset the loss of portability to, say, MacOS. Note that according to perlport, fnord/glop/bibba works, or can be made to work, under Unix, Windows, DOS, OS/2, VMS, VOS and RiscOS.
The XP folks wisely warn against designing in extra functionality "just in case"

Writing from the middle of an XP-to-Linux port

I know couple of meanings of XP: 1) a range of disk servers sold by HP, 2) a version of an OS made in the Pacific Northwest, 3) extreme programming. I'm pretty sure you aren't using "XP" in meaning 1). But I can't figure out whether you mean meaning 2) or meaning 3).

Abigail

In reply to Re: "But I'm never going to..." by Abigail-II
in thread "But I'm never going to..." by water

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.