summaryrefslogtreecommitdiff
path: root/META.yml
Commit message (Collapse)AuthorAgeFilesLines
* Bump version for 5.37.12Steve Hay2023-04-201-1/+1
|
* Bump version to 5.37.11, update Module-CoreListYves Orton2023-03-211-1/+1
| | | | | | | | | | Module-CoreList was synced with CPAN and had its version in Porting/Maintainers.pl updated. Module-CoreList was also updated by running: ./perl -Ilib Porting/corelist.pl cpan With some manual fixups afterwards to make it pass test.
* Bump the perl version in various places for 5.37.10Karen Etheridge2023-02-201-1/+1
|
* bump version for 5.37.9reneeb2023-01-211-1/+1
|
* Bump the perl version in various places for 5.37.8Richard Leach2022-12-201-1/+1
|
* Bump the perl version in various places for 5.37.6Max Maischein2022-11-201-1/+1
|
* Bump the perl version in various places for 5.37.6Todd Rinaldo2022-10-241-1/+1
|
* Move Math-Complex from cpan/ to dist/Karl Williamson2022-10-011-0/+1
| | | | This module is now being maintained by p5p now.
* Bump the perl version in various places for 5.37.5Karen Etheridge2022-09-201-1/+1
|
* Bumping perl version in various places for 5.37.4Neil Bowers2022-08-201-1/+1
|
* Bump version to 5.37.3Nicolas R2022-07-211-1/+1
|
* Dump perl version everywhere to 5.37.2Matthew Horsfall2022-06-201-1/+1
| | | | | This attempted to change sv_inline.h, but those were clearly wrong!
* bump version to v5.37.1: now open for businessRicardo Signes2022-05-271-1/+1
|
* bump version to v5.37.0Ricardo Signes2022-05-271-1/+1
|
* bump version to v5.36.0 (RC0)Ricardo Signes2022-05-201-1/+1
|
* Bump version for 5.35.12Steve Hay2022-04-201-1/+1
|
* Bump version for 5.35.11Sawyer X2022-03-201-1/+1
|
* bump version for 5.35.10reneeb2022-02-201-1/+1
|
* Bump the perl version in various places for 5.35.9Nicolas R2022-01-201-1/+1
|
* Make spelling of values for 'FILES' consistentJames E Keenan2022-01-101-49/+2
| | | | | | | | | | | While developing a program which require-s Porting/Maintainers.pl for the data in %Modules, I noticed that the entries for two modules' 'FILES' key-value pairs were spelled with a trailing slash. All other 'FILES' KVPs omitted the trailing slash. For consistency, let's omit the trailing slash. Once that's done, two invocations of "./perl -Ilib Porting/makemeta -y" were needed to make 'make test_porting' happy.
* Bump the perl version in various places for 5.35.8Neil Bowers2021-12-211-1/+1
|
* Bump the perl version in various places for 5.35.7Richard Leach2021-11-211-1/+1
|
* Bump version to 5.35.6Leon Timmermans2021-10-211-1/+1
|
* Bump versions from v5.35.4 to v5.35.5Matthew Horsfall2021-09-201-1/+1
|
* Bump the perl version in various places for 5.35.4Karen Etheridge2021-08-221-1/+1
|
* Bump the perl version in various places ready for 5.35.3Neil Bowers2021-07-241-1/+1
|
* Bump the perl version in various places for 5.35.2Max Maischein2021-06-201-1/+1
|
* mark test modules (found in ext/*/t/) as no_indexTony Cook2021-05-241-0/+34
| | | | fixes #18632
* Bump the perl version in various places for 5.35.1Max Maischein2021-05-231-1/+1
| | | | | Ideally, this would've been done earlier in the process of developing 5.35, but here we are
* Bump to 5.35.0:Sawyer X2021-05-211-1/+1
| | | | | | * Apparently, first you bump, then you update perldelta. * 5.35.0 *might* be released tomorrow (likely) but not certainly. * I've set it to tomorrow so Module::CoreList won't be upset.
* Bump perl version in various places for 5.34.0Sawyer X2021-05-041-1/+1
|
* Bump the Perl version to 5.33.9Nicolas R2021-03-201-1/+1
|
* bump version to 5.33.8reneeb2021-02-201-1/+1
|
* Bump version to 5.33.7Richard Leach2021-01-211-1/+1
|
* regen META.ymlPaul "LeoNerd" Evans2021-01-041-0/+1
|
* Bump version to 5.33.6Max Maischein2020-12-201-1/+1
|
* Bump version to 5.33.5Tom Hukins2020-11-201-1/+1
|
* Bump version to 5.33.4Steve Hay2020-10-201-1/+1
|
* Bump the perl version in various places for 5.33.3Sawyer X2020-09-211-1/+1
|
* Bump the perl version in various places for 5.33.2Karen Etheridge2020-08-201-1/+1
|
* Bump the perl version in various paces for 5.33.1Sawyer X2020-07-171-1/+1
|
* Bump to 5.33.0Sawyer X2020-06-281-1/+1
|
* Bump perl version in various places for 5.32.0Sawyer X2020-05-291-1/+1
|
* Bump the perl version in various places for 5.31.12Sawyer X2020-04-291-1/+1
|
* Bump back to 5.31.11, if we need to release itSawyer X2020-04-091-1/+1
|
* Bump version to 5.32.0Sawyer X2020-03-211-1/+1
|
* Bump the perl version in various places for 5.31.10reneeb2020-02-211-1/+1
|
* Make it possible to remove a closed IO::Socket handle from IO::Select.Todd Rinaldo2020-02-041-0/+1
| | | | Fixes #17447
* Bump the perl version in various places for 5.31.9Matthew Horsfall2020-01-201-1/+1
|
* Loading IO is now threadsafe, avoiding the core bug reported as GH #14816.Nicholas Clark2020-01-191-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Re-implement getline() and getlines() as XS code. The underlying problem that we're trying to solve here is making getline() and getlines() in IO::Handle respect the open pragma. That bug was first addressed in Sept 2011 by commit 986a805c4b258067: Make IO::Handle::getline(s) respect the open pragma However, that fix introduced a more subtle bug, hence this reworking. Including the entirety of the rest of that commit message because it explains both the bug the previous approach: See <https://rt.cpan.org/Ticket/Display.html?id=66474>. Also, this came up in <https://rt.perl.org/rt3/Ticket/Display.html?id=92728>. The <> operator, when reading from the magic ARGV handle, automatic- ally opens the next file. Layers set by the lexical open pragma are applied, if they are in scope at the point where <> is used. This works almost all the time, because the common convention is: use open ":utf8"; while(<>) { ... } IO::Handle’s getline and getlines methods are Perl subroutines that call <> themselves. But that happens within the scope of IO/Handle.pm, so the caller’s I/O layer settings are ignored. That means that these two expressions are not equivalent within in a ‘use open’ scope: <> *ARGV->getline The latter will open the next file with no layers applied. This commit solves that by putting PL_check hooks in place in IO::Handle before compiling the getline and getlines subroutines. Those hooks cause every state op (nextstate, or dbstate under the debugger) to have a custom pp function that saves the previous value of PL_curcop, calls the default pp function, and then restores PL_curcop. That means that getline and getlines run with the caller’s compile- time hints. Another way to see it is that getline and getlines’s own lexical hints are never activated. (A state op carries all the lexical pragmata. Every statement has one. When any op executes, it’s ‘pp’ function is called. pp_nextstate and pp_dbstate both set PL_curcop to the op itself. Any code that checks hints looks at PL_curcop, which contains the current run-time hints.) The problem with this approach is that the (current) design and implementation of PL_check hooks is actually not threadsafe. There's one array (as a global), which is used by all interpreters in the process. But as the code added to IO.xs demonstrates, realistically it needs to be possible to change the hook just for this interpreter. GH #14816 has a fix for that bug for blead. However, it will be tricky (to impossible) to backport to earlier perl versions. Hence it's also worthwhile to change IO.xs to use a different approach to solve the original bug. As described above, the bug is fixed by having the readline OP (that implements getline() and getlines()) see the caller's lexical state, not their "own". Unlike Perl subroutines, XS subroutines don't have any lexical hints of their own. getline() and getlines() are very simple, mostly parameter checking, ending with a one line that maps to a single core OP, whose values are directly returned. Hence "all" we need to do re-implement the Perl code as XS. This might look easy, but turns out to be trickier than expected. There isn't any API to be called for the OP in question, pp_readline(). The body of the OP inspects interpreter state, it directly calls pp_rv2gv() which also inspects state, and then it tail calls Perl_do_readline(), which inspects state. The easiest approach seems to be to set up enough state, and then call pp_readline() directly. This leaves us very tightly coupled to the internals, but so do all other approaches to try to tackle this bug. The current implementation of PL_check (and possibly other arrays) still needs to be addressed.