This is a better match for what File::Spec is doing: 
package XPlat;
use strict;
my $OS_TYPE = $^O eq 'MSWin32' ? 'win' :
              ($^O eq 'nonstop_kernel' ? 'nsk' : 'unix');
push @ISA, "XPlat::$OS_TYPE";

sub XPlat::win::fn  { print "windows version of function\n" }
sub XPlat::nsk::fn  { print "nsk version of function\n"     }
sub XPlat::unix::fn { print "unix version of function\n"    }

package main;

XPlat->fn(); # calls function in whichever package is appropriate

[download]

As a bonus, you can use inheritance to share common methods by moving them up to a superclass, or produce other effects by creating additional subclasses.

In reply to Re: Seeking good ways to structure cross-platform code by simonm
in thread Seeking good ways to structure cross-platform code by eyepopslikeamosquito

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.