| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
Add Unicode::Regex::Set to the list of known CPAN modules.
Reflow a verbatim block to fit within the column limit.
|
| | |
|
| |
|
|
|
| |
a missing word, remove L<> from a verbatim block, add L<> for a module,
clarify wording
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This makes the \$ prototype’s parsing the same as the second argument
to read(), making it possible to create a custom myread() function
that has the same syntax.
This is handled in two places in the prototype-parsing code, to avoid
calling scalar() on the op if another character in \[...] will accept
it. I don’t know what the consequences of that would be. So it calls
Perl_op_lvalue_flags in the $ case only if it is not inside brackets.
Then in the ] case it checks to see whether there was a $.
OP_READ, not OP_ENTERSUB, is passed as the type to
Perl_op_lvalue_flags, since OP_ENTERSUB would allow sub foo(\$) to
accept an array as an argument. OP_RECV and OP_SYSREAD would have
worked, too.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is something that commit e08be60 missed, though it never worked
properly, even in 5.14, as explicit return from lvalue subs used to
copy return values.
As the commit message for e08be60 states, returning a scalar itself
from an lvalue sub does not work if it is a pad variable with a refer-
ence count of 1, because the sub-popping code clears it on exit.
The one code path that did not account for this was list lvalue con-
text (real lvalue context, not just potentially lvalue). The only
observable effect this has is that assigning to a magic pad variable
returned from a subroutine in list context will not trigger set-magic.
This commit fixes it and also adds tests for returned magic pad vars
in all combinations of list/scalar lvalue/ref context.
|
| |
|
|
| |
This causes the regex engine to take advantage of the study data.
|
| |
|
|
|
| |
This causes explicit return in lvalue context to die the way implicit
return does. See the tests and the perldelta entry in the diff.
|
| |
|
|
|
|
| |
Instead, take advantage of the "can't edit in place" code path of pp_subst
which writes to a new scalar, and that pp_substcont always leaves the original
intact, writing to a new scalar.
|
| |
|
|
|
| |
For threaded platforms, this reduces the object code size significantly, and
should slightly reduce CPU usage.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
[DELTA]
2.037 22 June 2011
* IO::Uncompress
- get globmapper tests working on VMS
[RT# 68926]
* IO::Uncompress::Unzip
- Fixed limitation where Streamed Stored content was not supported.
|
| |
|
|
|
|
|
|
| |
[DELTA]
2.037 22 June 2011
* No Changes
|
| |
|
|
|
|
|
|
| |
[DELTA]
2.037 22 June 2011
* No Changes
|
| |
|
|
|
|
|
|
|
| |
[DELTA]
Changes for 0.72 Wed Jun 22 12:29:59 BST 2011
=================================================
* Added IPC::Open3 support for capturing STDOUT/STDERR
on MSWin32, prefer this over IPC::Run
|
| |
|
|
|
|
|
|
| |
This is something that ‘sub foo :lvalue;’ declarations do. This brings
attributes.pm in line with them.
See commits fff96ff and 885ef6f, ticket #68758, and
<364E1F98-FDCC-49A7-BADB-BD844626B8AE@cpan.org>.
|
| |
|
|
|
|
| |
This makes many documents more consistent in their pod formatting. Don't trim
blank lines between verbatim blocks and =item, as removing them makes the (raw)
pod harder to read.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
[DELTA]
2.036 18 June 2011
* IO::Compress::Zip & IO::Uncompress::Unzip
- Added support for LZMA (method 14) compression/uncompresion.
* IO::Compress::Unzip
- Fixed CRC issue when compression is Store or Bzip2 and Strict option
is set.
* IO::Compress::Zip
- Fixed Zip64 issue where the content size is exactly 0xFFFFFFFF
|
| |
|
|
|
|
|
|
| |
[DELTA]
2.036 6 May 2011
* Added offset parameter to CRC32
|
| |
|
|
|
|
|
|
| |
[DELTA]
2.036 18 June 2011
* No Changes
|
| |
|
|
|
|
|
|
|
|
| |
This is something that commit 885ef6f missed. See ticket #68758 and
the perldelta diff in this commit.
I thought that the prototype-application inconsistencies mention in
<2C7C1BF5-A814-4F5E-B10E-E431B71BA8CA@cpan.org> would get in the way
of this, but I found that the easiest way to fix it actually did not
change any of that. So those issues can wait till another day.
|
| |
|
|
|
|
|
| |
Porting/perldelta_template.pod is exempt from t/porting/podchecker.t, but when
its contents are copied as pod/perldelta.pod, that file is not. This change
reduces the amount of work the release manager needs to do to create a new
perldelta.
|
| | |
|
| |
|
|
|
|
| |
The intent of splice(@a,MAX_LEN) is quite clearly to truncate
the array if it's too large. There's no reason to warn if it's
currently smaller than the max length.
|
| | |
|
| |
|
|
|
| |
88fb56ecc95f23db used 'pod/perldelta.pod' instead of abs_from_top(), and broke
the build on Win32, which runs buildtoc from the win32 directory.
|
| |
|
|
|
| |
For 80 columns, this collection of spacing changes keeps all
lines in this pod from wrapping.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
As the edited perldelta is now always pod/perldelta.pod (instead of a file with
version numbers in it), we don't need a 'D' flag to mark it. As perldelta.pod
contains within itself the number of the version it refers to, we can use that
to infer the 'd' flag for the target filename.
This simplifies the release manager's tasklist for version bumping.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
We have the CUSTOMIZED field in Maintainers.pl for indicating where we
expect blead to differ from a CPAN tarball. This commit documents that
in perlhack and makes core-cpan-diff more aggressive about checking it
and reporting about it.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
