On Thu May 26 21:38:50 2016, sprout wrote:
$ perl -we '(vec%0,0,1)=0'
Use of uninitialized value within %0 in vec at -e line 1.
Can't coerce HASH to string in aassign at -e line 1.
That output is nonsensical.
Thank you for finding one. :-)
On Thu May 26 18:52:05 2016, [email protected] wrote:
A git bisect was performed and
reported the following, which appears to be when the assert was
initially added.
217f6fa330a187be32a68556507e3165b8747f55 is the first bad commit
commit 217f6fa330a187be32a68556507e3165b8747f55
Author: Father Chrysostomos <[email protected]>
Date: Fri Jul 19 08:51:47 2013 -0700
sv.c: Assert that sv_[ivp]v are not passed aggregates
The lack of assertions can hide bugs. See 32a609747bffb for instance
That assertion was added specifically to find bugs like this:A git bisect was performed and
reported the following, which appears to be when the assert was
initially added.
217f6fa330a187be32a68556507e3165b8747f55 is the first bad commit
commit 217f6fa330a187be32a68556507e3165b8747f55
Author: Father Chrysostomos <[email protected]>
Date: Fri Jul 19 08:51:47 2013 -0700
sv.c: Assert that sv_[ivp]v are not passed aggregates
The lack of assertions can hide bugs. See 32a609747bffb for instance
$ perl -we '(vec%0,0,1)=0'
Use of uninitialized value within %0 in vec at -e line 1.
Can't coerce HASH to string in aassign at -e line 1.
That output is nonsensical.
Thank you for finding one. :-)
$ perl -we '(vec $_+1,0,1)=0'
Can't modify addition (+) in list assignment at -e line 1, at EOF
Execution of -e aborted due to compilation errors.
$ perl -we 'vec($_+1,0,1)=0'
Can't modify addition (+) in scalar assignment at -e line 1, at EOF
Execution of -e aborted due to compilation errors.
It’s prototype currently is effectively ‘\[$@%*]$$’, but it should probably be ‘\$$$’.
Also, those ‘Can't modify’ messages cite the wrong op (list/scalar assignment instead of vec).
--
Father Chrysostomos
---
via perlbug: queue: perl5 status: open
https://rt.perl.org/Ticket/Display.html?id=128260