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

Re: PSC #025 2021-06-18 minutes

Thread Previous | Thread Next
From:
Dan Book
Date:
June 28, 2021 00:48
Subject:
Re: PSC #025 2021-06-18 minutes
Message ID:
CABMkAVXzgKb=kbR2UkvExpj+rpRU9RhOqvUscsPtQavFdm8kaw@mail.gmail.com
On Sun, Jun 27, 2021 at 6:45 PM Darren Duncan <darren@darrenduncan.net>
wrote:

> On 2021-06-27 3:31 p.m., Paul "LeoNerd" Evans wrote:
> >    Existing modules: perl >= 5.16, for the most part. A few exceptions
> >      exist for really high-river ones (e.g. List::Util, IO::Socket::IP)
> >      but for most of these, taking 5.16 onwards means at least basic
> >      support of try/catch, async/await, Object::Pad via syntax modules,
> >      even though the signatures aren't yet available.
> >
> >    I have so far not yet encountered a case where anyone cared about a
> >    perl older than 5.16.
>
> DBI still cares about Perl from 5.8.1 and up; I recently asked and there
> are no
> plans to change this.
>
> Similarly, DBI wrappers like DBIx::Class also care about Perl 5.8.1.
>
> For my part, I plan to release brand new modules in that space, and on one
> hand
> since they're brand new I was thinking of just defaulting to the latest
> Perl
> version at the time eg 5.34 and then ratchet it down if people explicitly
> ask
> for that.
>
> On the other hand the oldest I would ever want to support is the same
> version
> that DBI itself does BECAUSE DBI itself does, and in theory any features I
> need
> from Perl were present in 5.8.1 and its just syntactic niceties that came
> afterwards.  Except I would round to 5.8.0 because 1 seems arbitrary in my
> case.
>

In this case (and similarly for 5.10.0) the 1 is unfortunately not
arbitrary; 5.8.0 is horribly broken, and luckily did not find widespread
usage.

-Dan

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