Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Putting the ``Backwards'' in ``Backwards Compatibility''? 1 Comment More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Can anyone (from p5p, maybe) look at Perl today, and tell us what the likely breaking points are? Functions will change their return values? Syntax changes? Garbage collection?

    Maybe a line should be drawn clearly in the documentation between what you can rely on and what behaviour is considered "undefined" or a "mere side-effect of a particular operation which you really can't rely on".

    Hmm. It is an interesting question.

    Maybe "Perl" should be defined separately (somehow) from "perl". Much like there are several implementations of Java, there *could* be several compliant implementaions of Perl. In the process of doing that, you'd know what Topaz must not break.

    Would that be practical? I wonder...
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.