Front page | perl.perl5.porters |
Postings from March 2012
On Tue Mar 27 18:38:01 2012, jkeenan wrote:
> On Sun Feb 01 19:09:41 2004, davem@fdisolutions.com wrote:
> > On Thu, Jan 29, 2004 at 07:39:59AM -0000, David Dyck wrote:
> > > Recent bleading edge version have started causing
> > > Regexp::Common to start issuing warnings that they
> > > didn't before.
> > >
> > > $ perl -we 'use Regexp::Common'
> > > Variable "$s" is not available at (re_eval 47) line 1.
> > > Variable "$x" is not available at (re_eval 47) line 1.
> > >
> > > Does this indicate a bug in perl or in Regexp::Common?
> > > (the error message makes it a bit difficult to
> > > identify the offending line(s) of code.
> > >
> > > make test with Regexp-Common-2.113 passes all test, but
> > > it too issues many warnings during the tests.
> > >
> [snip]
> >
> > Well, the use of lexical variables in conjunction with (?{...})
> > is currently highly buggy. My recent closure patches to bleedperl
> > now tend to cause warnings where before things just silently did the
> > wrong
> > thing.
> >
> > It's on my List Of Things To Do, but probably not any time soon (since
> > the
> > regex engine scares the life out of me).
> >
> >
>
> I just installed Regexp-Common-2011121001 on top of Perl 5.14.2
> (Linux/i386), using the 'cpan' utility. I got no warnings during 'make
> test'. Nor did I get warnings during 'prove -v t/*.t'. Nor did I get
> any warnings saying:
>
> perl -we 'use Regexp::Common'
>
> I suspect that the bug was fixed at some point in the last eight years
> and recommend that the ticket be closed.
The underlying perl bug that the older Regexp::Common triggered I
believe is still present, but is part of what Dave Mitchell is currently
working on.
--
Father Chrysostomos
---
via perlbug: queue: perl5 status: open
https://rt.perl.org:443/rt3/Ticket/Display.html?id=25655
Thread Previous