Thx,

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)

In reply to Re^2: Parsing and translating Perl Regexes by LanX
in thread Parsing and translating Perl Regexes by LanX

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.