| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
version.pm was changed by 61a0cb1c57a82d328c88c2dd525c91495edb2db9
and Jesse confirms that the $VERSION should be bumped as a result.
|
|
|
|
| |
Cf. 71eaafb1e6768e777bc805cc8490b55c6e77da64
|
| |
|
| |
|
|
|
|
|
|
|
| |
Change from a value/return offset pointer to passing a Unicode offset, and
returning a byte offset. The optional length value/return pointer remains.
Add a flags argument, passed to SvPV_flags(). This allows the caller to
specify whether mg_get() should be called on sv.
|
|
|
|
| |
(Tweaking 777f7c561610dee6.)
|
|
|
|
| |
available for the pos and len arguments, with safe conversion to STRLEN where it's smaller than an IV.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
linking miniperl
SystemTaps' dtrace binary lives in /usr/bin, so add a check to Configure
for that.
Additionally link the dtrace .o file into miniperl, which is an issue
with SystemTap and also reported on p5p to affect OpenSolaris in
Signed-off-by: H.Merijn Brand <h.m.brand@xs4all.nl>
|
| |
|
| |
|
|
|
|
|
| |
This warning is emitted by perl when re-throwing the exception, so add a
TODO test to suppress it. However, fixing that will imply a core change.
|
| |
|
| |
|
|
|
|
|
| |
This patch was reviewed with Larry Wall via IRC. His stipulation was
that both historical glossses be preserved to humorous effect.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
An exception thrown from a closure gets lost.
I've boiled it down to this:
perl -MSafe -e 'Safe->new->reval(q{sub { die @_ }})->(qq{ok\n})'
That should die with "ok".
The problem is that the closure that wraps any returned code ref if
threads are enabled is acting as an eval block so hiding the exception.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
That bug happens when we detect a compilation error in the statement
being parsed, and when the continuation of the parsing of that same
statement needs to load the file unicore/Name.pl via charnames.pm.
In that case perl gets confused, fails to parse Name.pl because
the parser is already in error, and also fails to properly rewind
to a normal error-reporting state.
This patch does not attempt to fix the whole error-reporting process;
instead, it simply prevents perl from trying to load charnames if it has
already recorded a parse error. So, in a way, it hides the bug under
the carpet. However, this is a safe fix, suitable for a code-freeze
stage.
|
| |
|
| |
|
|
|
|
| |
documented at the time. Resolves [perl #62522]
|
|
|
|
| |
builds. See RT #71504 for the mess that this is avoiding.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
$ ./perl -lwe '$a = ${qr//}; $a = 2; print re::is_regexp(\$a)'
1
It is possible for arbitrary SVs (eg PAD entries) to be upgraded to
SVt_REGEXP. (This is new with first class regexps)
Whilst the example above does not SEGV, it will be possible to write
code that will cause SEGVs (or worse) at the point when the scalar is freed,
because the code in sv_clear() assumes that all scalars of type
SVt_REGEXP *are* regexps, and passes them to pregfree2(), which assumes that
pointers within are valid.
|
|
|
|
| |
Please keep them sorted
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* 'blead' of ssh://perl5.git.perl.org/gitroot/perl:
Warn people not to set PERL_CORE in XS
In embed.fnc the 'E' flag should imply 'X', but doesn't.
revise perldelta note on strict and lax version rules
expand flag descriptions in in embed.fnc
alphabetically sort flag descriptions in embed.fnc
[perl #72156]: substitute `less -R' for `less' for groff's new usage
INSTALL doc fix: calling the test suite using -MTestInit changed since it moved to top level (which happened in commit 30b6e59101b252c20a6b50b95203d1e2c6016604)
changed "an UTF..." to "a UTF..." in all Pods
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
For each flag, try to list what precise effects that flag has
|
| | |
|
| |
| |
| |
| |
| | |
of ANSI escape codes by setting $Config{less} (and thereby
$Config{pager}).
|
| |
| |
| |
| | |
moved to top level (which happened in commit 30b6e59101b252c20a6b50b95203d1e2c6016604)
|
| | |
|
| |
| |
| |
| |
| |
| | |
Note to the deprecation police: this is not a language construct
deprecation. Just a bit of healthy advice about coding style.
Who knows. In a decade, this may be the lynchpin of "postmodern perl".
|
|/ |
|
| |
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* 'blead' of ssh://perl5.git.perl.org/gitroot/perl:
move version details to version::Internals and other clean up
document version::is_strict/is_lax
Document usage of version regexps
Export and document is_lax and is_strict functions
note that delete/exists ARRAY_ELEM should be avoided
Don't try to calculate a time over the conservative failure boundary.
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
Move the discussion of what each regexp coveres to version::Internals
and limit the discussion in the main POD to just include examples.
|
| |
| |
| |
| |
| |
| |
| |
| | |
Allow the is_lax and is_strict functions to be optionally
exported to the caller's namespace (without having to use Exporter).
Document the usage of is_lax and is_strict, plus nuke some trailing
spaces.
|
| |
| |
| |
| | |
addreses final determination of http://rt.perl.org/rt3/Public/Bug/Display.html?id=72064
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Otherwise gmtime(2**66) will cause a very, very, very long loop and
DOS Perl.
Add a test that very, very large times don't send gmtime and localtime into a loop
Had to fix some revealed mistakes in op/time.t when warnings were turned on.
Fix Time::gmtime and Time::localtime tests to match the new limits of gm/localtime.
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
blessing filehandles into FileHandle
It turns out that it's not quite as simple as blessing into IO::File.
If you do (just) that, then it breaks any existing code that does
C<require IO::Handle;> to allow it to call methods on file handles,
because they're blessed into IO::File, which isn't loaded. (Note this code
doesn't assume that methods in IO::Seekable are there to be called)
So, it all should work if you also set @IO::File:::ISA correctly?
That way, code that assumes that methods from IO::Handle can be called will
work. However, gv.c now starts complaining (but not failing) if IO::Handle,
IO::Seekable and Exporter aren't present, because it goes looking for
methods in them.
So the solution seems to be to set @IO::File::ISA *and* create (empty)
stashes for the other 3 packages. Patch appended, but not applied.
|
| |
|
|
|
|
|
|
|
|
| |
I chatted with Gisle and he confirmed that this didn't fix a
release-blocking issue. Since we're frozen for 5.12, he agreed that we
should back it out.
This reverts commit 5e58db16ffcf34442d0ba4b645757884324e35c2.
|