Ansi C is portable to different platforms without problems if you avoid the things that are specified as implementation defined as well.

That, after all, is the point of having a standard.

The problem with unportable C code isn't because every coder is following the standard. The problem is coders targetting their compiler, and (ab)using its extensions. And then of course, there are the different libraries.

Sure, there are some differences from one version to another, but if you restrict yourself to what is documented in the 2nd edition Camel (and avoid the aforementioned inherently-unportable things, such as backticks and link, and hardcoded filenames and paths), it will pretty much run unmodified and with the same semantics on any version from 5.003 forward, on any operating system that has Perl5.
I've yet to write a C program that broke because I upgraded my compiler, or that I had to modify because it needed to be compiled on an older version of the compiler (although I've had to rewrite large portions of C programs because of kernel upgrades). OTOH, every upgrade of perl has broken some program of mine, somewhere.

In reply to Re^2: Ansi Perl by Anonymous Monk
in thread Ansi Perl by Eyck

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.