| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
[perl #130247] Perl_rpeep(OP *): Assertion `oldop' failed
the 'x 0' optimising code in rpeep didn't expect the repeat expression
to occur on the op_other side of an op_next chain.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Use set_up_inc when require.pl is loaded
move plan outside of BEGIN block
when no tests are run at BEGIN time.
Using set_up_inc allow to run these tests under minitest
but also compile them using B::C.
This also has the advantage to use a single
control point for @INC setup.
Note: some tests cannot use 'require test.pl',
unshfit is then used for them.
|
|
|
|
|
| |
Some of this is ugly, but that’s because I wrote a one-liner to do
it. It’s good enough for practical purposes.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Recent improvements to MEXTEND() etc means that the above is now caught and
panics rather than crashing. However, the panic is:
panic: av_extend_guts() negative count (-9223372036854775681)
which is safe, but not pretty. This commit makes it croak instead with:
Out of memory during stack extend
Basically Perl_stack_grow() adds an extra 128 bytes of headroom to the
amount it actually extends the stack by. Check in stack_grow() itself
whether this has wrapped, rather than leaving it to av_extend_guts(),
which can only give a generic panic message.
|
|
|
|
|
|
| |
Unfortunately, running out of memory in safesysmalloc() and
safesysrealloc() doesn't produce a catchable croak(), so remove the
test.
|
|
|
|
|
|
|
| |
Sith IV/UV larger than Size_t, the overflow can be detected earlier,
so the message varies.
The error is still reported with a croak(), so it can be captured.
|
| |
|
|
|
|
|
|
| |
When a57276195 changed the eq to is(), the comment was not updated.
The test still works. (I tried introducing the bug it was testing
for via SP--, and it failed as expected.)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
(...)x... is marked as a list at compile time and given a pushmark,
before the context is known. If it turns out to be called in scalar
or void context after all, then pp_repeat has to handle the mark that
has been pushed on to the markstack.
It was not handling the mark for overloading. Nor was it handling
void context correctly at all. (The stack may have an empty list, in
which case we call FETCH on a potentially tied stack item that has
nothing to do with us.)
I tested it in void context, because I plan to undo the listification
when scalar context is applied, for speed.
|
|
|
|
| |
This allows foreach(($#array)x$count) { $_++ } to work as expected.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
(undef,undef,undef,$foo,$bar)=that_function();
can now be written as
((undef)x3, $foo, $bar) = that_function();
Furthermore, (($a)x$assign_to_a,$b) = @c will include $a in the list
of variables ta assign to if $assign_to_a is 1, assign $c[0] to $b
if $assign_to_a is 0. In other words, assuming $assign_to_a is 1 or
0, it is equivalent to:
($assign_to_a ? ($a, $b) : $b) = @c
|
|
|
|
|
|
|
|
|
| |
Aka #7505, the bug was that list repeat didn’t copy its
elements. But list repeat hasn’t copied its elements for
years now, and code could be relying on the current
behaviour of foreach(($var)x2) { ... } which aliases $_
to $var twice. We also have tests for the current
behaviour.
|
|
|
|
|
| |
So that \(("$a")x2) will give two references to the same scalar, the
way that \(($a)x2) does.
|
|
|
|
|
| |
plus a regular (not to-do) test for an lvalue sub case that already
works properly.
|
| |
|
|
|
|
|
| |
This fixes [perl #35885] qw and x operators doesn't mix
p4raw-id: //depot/perl@24560
|
|
|
|
|
| |
(as suggested by Jarkko.)
p4raw-id: //depot/perl@22922
|
|
|
|
|
| |
Message-ID: <40C4A156.5030205@iki.fi>
p4raw-id: //depot/perl@22904
|
|
|
|
|
|
|
|
| |
idea. Disable it. But add tests for this :
Subject: Re: [perl #27811] (@x) x -1 is a panic
Message-ID: <20040321152704.GA9041@petdance.com>
p4raw-id: //depot/perl@22549
|
|
|
|
|
|
| |
Tiny problem in the test for 20011113.110: I hope
'my $x= [("foo") x 1]' was never going to produce [qw(foo foo)] :-)
p4raw-id: //depot/perl@13077
|
|
|
|
|
| |
Message-ID: <20011114163825.D6519@blackrider>
p4raw-id: //depot/perl@12999
|
|
|
|
|
| |
Message-ID: <20010324143309.B17734@puffinry.freeserve.co.uk>
p4raw-id: //depot/perl@9325
|
|
|
|
|
| |
(what patch levels of the compilers fix them).
p4raw-id: //depot/cfgperl@3258
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
a Digital C compiler optimizer bug that broke the 'x'
operator under certain circumstances. See t/op/repeat.t
test #20 for graphic details. Reported in
From: Gisle Aas <gisle@aas.no>
To: Mark Martinec <Mark.Martinec@nsc.ijs.si>
Cc: ach@xray.mpe.mpg.de, cpan-testers@perl.org, perl5-porters@perl.org
Subject: Re: Digest-MD5-2.00 test fails on DEC Alpha - a patch
Date: 18 Dec 1998 14:27:40 +0100
Message-ID: <m37lvpa8c3.fsf@furu.g.aas.no>
and discussed further in the thread
From: Jarkko Hietaniemi <jhi@iki.fi>
To: Gisle Aas <gisle@aas.no>
Cc: Mark Martinec <Mark.Martinec@nsc.ijs.si>, ach@xray.mpe.mpg.de,
cpan-testers@perl.org, perl5-porters@perl.org
Subject: x operator broken in DEC Alpha for 8-bit characters (Re: Digest-MD5-2.00 test fails on DEC Alpha - a patch)
Date: Fri, 18 Dec 1998 16:18:37 +0200 (EET)
Message-ID: <13946.25661.193449.138023@alpha.hut.fi>
p4raw-id: //depot/cfgperl@2498
|
|
|
|
| |
[editor's note: from history.perl.org. The sparc executables
originally included in the distribution are not in this commit.]
|
|
So far, 4.0 is still a beta test version. For the last production
version, look in pub/perl.3.0/kits@44.
|