Beefy Boxes and Bandwidth Generously Provided by pair Networks
Your skill will accomplish
what the force of many cannot
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
Thanks! =)

> I offer up a solution using a guard.

I think you are a little too concerned about the redirection thing. I know it looks weird (at least it did the first time for me) but it's well documented in the perldocs.

Direct hooks into the regex-engine OTOH would be nice...

> "online analyzers which are easily fooled".

many online solutions think PCRE means PCRE...

> It'll at least take care of the tokenizing for you.

actually there more levels of tracing-info which use re qw/Debug .../ may supply. (I still have to dig into perlreguts to understand it completely)

I like the fact that Perl does the hard thing for me ... and I have this nagging feeling that only Perl can parse Perl... ;-)

One may trust into specifications, but regarding Perl I think direct control is better. ¹

At second thought translating to other engines is a very ambitious task, I think I should start with a simple beautifier which translates "line-noise" to a '/x'-option multiline expression.

Ok YAPE::Regex::Explain could possibly be patched for this.

Cheers Rolf

( addicted to the Perl Programming Language)

¹) kind of quoting a big administrator ;-)


In reply to Re^4: 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":



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others cooling their heels in the Monastery: (3)
As of 2024-03-29 04:35 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found