in reply to Re: Parsing and translating Perl Regexes
in thread Parsing and translating Perl Regexes
I didn't redirect warn() b/c I didn't expect it to be used by the underlying C code.
And indeed your code doens't work! (unfortunately)
$log will be undefined ... the output you are getting is just directly written to STDERR.
Just try to change it before it's written, like lowercasing with lc().
> Is use re debug; output stable enough for automated parsing?
we'll see, some stuff isn't escaped (like EXACT <>> (42) to match ">") so hopefully the regexes can still match them by surrouding context.
Do I have a better choice? (well thats why I started this thread =)
Cheers Rolf
( addicted to the Perl Programming Language)
|
---|
Replies are listed 'Best First'. | |
---|---|
Re^3: Parsing and translating Perl Regexes
by kennethk (Abbot) on Nov 04, 2013 at 21:02 UTC | |
by LanX (Saint) on Nov 05, 2013 at 12:21 UTC |