Perhaps you could determine the version of perl during the makefile building process, set a proper variable, and then run the XS code through some kind of preprocessor? I'm not sure how ExtUtils::MM does things, so I can't comment on the difficulty. Considering all the work that DBD::Oracle does when you do perl Makefile.PL, it must be possible. 
PERL_VER = `perl -e 'print $['`
preprocess:
  @cpp -DPERL_VAR=${PERL_VAR} forks.xs forks.i 
  @mv forks.i forks.xs

[download]
In forks.xs, use happy fun #ifdefs to partition the code. What do you think?

In reply to Re: Forks.pm dilemma by Kageneko
in thread Forks.pm dilemma by liz

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.