Front page | perl.perl5.porters |
Postings from October 2016
On Tue Oct 18 01:01:21 2016, demerphq wrote:
> On 18 October 2016 at 03:17, Father Chrysostomos via RT
> <perlbug-followup@perl.org> wrote:
> > On Mon Oct 17 10:26:19 2016, brian.carpenter@gmail.com wrote:
> >> I'm not convinced that this is an actual bug,
> >
> > I think it is.
> >
> >> but #p5p was silent when I
> >> asked about it. Affects Perl back to 5.20.2 including v5.25.6
> >> (v5.25.5-114-g87af8d5). Valgrind fails pretty quickly but gdb just
> >> goes on
> >> forever.
> >>
> >> perl -e '/0'
> >
> > That is nonsensical code.
>
> Do you mean just the '/0' or the full pattern?
I do not know what happened, but the line that I quoted was:
perl -e '/(?{m}(0)},s\/\/\/})//0'
not:
perl -e '/0'
> With some editing I read the original code as being the same as
>
>
> (m/(?{
> m!(0)!,
> s!!!
> })/) / 0
I see now that I misread the code. the } for the m}} delimiter was what threw me off.
--
Father Chrysostomos
---
via perlbug: queue: perl5 status: open
https://rt.perl.org/Ticket/Display.html?id=129903
Thread Previous
|
Thread Next