develooper Front page | perl.perl5.porters | Postings from June 2009

RE: Perl 5.10.1

Thread Previous | Thread Next
From:
Jan Dubois
Date:
June 30, 2009 11:10
Subject:
RE: Perl 5.10.1
Message ID:
015001c9f9ae$084e6170$18eb2450$@com
On Tue, 30 Jun 2009, Marvin Humphrey wrote:
> In retrospect, perhaps it would have made sense to fork into new namespaces
> continually -- KinoSearch1, KinoSearch2, and so on.

I *strongly* believe that you should be doing this whenever you are
making incompatible API changes.  Bug fixes are of course a gray
area, but generally it should be a red flag whenever you have to change
old regression tests to make them pass with the current version of
the module.

Given the way the whole toolchain works, module names should be treated
as an _interface_ promise, and not just a generic human readable tag.

If you do this properly, then you can even load both MyModule1 and
MyModule2 into the same Perl interpreter, something you simply cannot do
with just version numbers that don't become part of package names.

Cheers,
-Jan


Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About