Language change and code breaks

Nick Efford nde at comp.leeds.ac.uk
Tue Jul 17 15:06:58 CEST 2001


On Mon, 16 Jul 2001 10:48:42 -0600,
Bjorn Pettersen <BPettersen at NAREX.com> wrote:

> Getting Python accepted in an organization as a viable alternative to
> Perl requires a lot of hard work. Once you've got a foothold it seems
> stupid to shoot yourself in the foot by introducing random
> incompatibilities that may or may not provide better traction for
> non-users (not to mention the hackish solutions to long division that
> would be introduced).

IIRC, aren't Perl-ers contemplating incompatibilities of
a similar degree for Perl 6? (albeit with some kind of
automated Perl 5 --> 6 conversion tool provided to ease
the transition...)

> I'm not against making this change per se, however, I think it should be
> in the context of an overhaul of the entire numerical system, and it
> definitely deserves a 3.0 labelling since that would indicate that there
> are incompatible changes involved with upgrading.

Yes - I also like the idea of using a 3.0 version number
to signal the importance of these changes.


Nick




More information about the Python-list mailing list