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

=?UTF-8?Q?Re=3a_Core=e2=80=99s_purpose?=

Thread Next
From:
Darren Duncan
Date:
November 27, 2021 00:04
Subject:
=?UTF-8?Q?Re=3a_Core=e2=80=99s_purpose?=
Message ID:
b44f0e52-2ff5-1625-f2a4-2573c29bde53@darrenduncan.net
And rightly so.  DBI is an ecosystem unto itself and complicated enough that it 
SHOULD remain separate from the Perl core.  Any candidates to add to core should 
be things that are very simple and small or that can reasonably only be 
implemented that way.  So I can see things like CSV support, but not DBI. -- 
Darren Duncan

On 2021-11-26 11:00 a.m., Joseph Brenner wrote:
> DBI and the major DBD modules have been obvious omissions for some time.
> 
> On 11/26/21, Neil Bowers <neilb@neilb.org> wrote:
>> Perlpolicy says "From time to time, a script, module, or set of modules will
>> prove so widely useful and/or so integral to the correct functioning of Perl
>> itself that it should be distributed with the Perl core".
>>
>> Given the "widely useful" criterion, there are definitely some additional
>> modules that I think we should include. CSV files are going to be with us
>> for a long time to come, and my guess is that many of us just directly use
>> Text::CVS_XS. That’s not a very inviting name though – much better would be
>> just "CSV". In this case it looks like we could transfer the indexing perms
>> for CSV (currently Csv, but they considered case-independently by PAUSE),
>> but that won’t always be true.
>>
>> I think we could usefully extend the entry in perlpolicy, to give more
>> explicit guidance on what sort of modules we want to bundle, and how that
>> should be done.
>>
>> As you say, where we want Perl to be considered "a great language for doing
>> X", then you should be able to "do X" out of the box.

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