develooper Front page | perl.perl5.porters | Postings from July 2020

Re: Supporting for N years rather than N versions

Thread Previous | Thread Next
Philip R Brenan
July 5, 2020 22:20
Re: Supporting for N years rather than N versions
Message ID:
One of the attractions of writing modules on CPAN is the idea that they
will be there for a very long time, possibly millenia.  If in fact it is
only for a decade or two this greatly diminishes the attraction of CPAN and
further weakens the case for using Perl. At the moment one can argue that
CPAN was there first, it is the biggest, the best, that it has been there
for decades, it will be there for many more, it endures through good times
and bad, it is part of our patrimony to future generations, that the effort
of writing stuff for CPAN is well worthwhile because it will be there for
ever.  But if v5 is only going to work for a few more years, then it is
time to move away from Perl now as quickly as possible to some other
language or system that does have the vision and will to carry our ideas
into the future.

On Sun, Jul 5, 2020 at 10:41 PM Darren Duncan <>

> On 2020-07-05 2:21 p.m., Paul "LeoNerd" Evans wrote:
> > In summary; I think we should be thinking about this in terms of "at
> > least N years", not "at least K major versions".
> I fully agree with this.
> Once a particular Perl standard/protocol version ceases to be the
> "current"
> version, it is from that point supported for "at least N years" worth of
> Perl
> interpreters.
> So that means for example, from the day the Perl 7.0.0 interpreter comes
> out,
> newly released Perl interpreters over the following at least N years will
> support "use v5" code.
> -- Darren Duncan


Phil <>

Philip R Brenan <>

Thread Previous | Thread Next Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at | Group listing | About