Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl-Sensitive Sunglasses

comment on

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

My things have come a long way since this thread. :-)

Id say hacking this into the regex engine is probably a good thing. And i suspect that its probably easier to do so than to hack PCRE into perl. Even perls own regex engine is not easily properly pluggable due to a lack of hooks into sv.c's re_dup(). I suspect that getting the PCRE engine would have the same problems. Which actually reminds me, we need to make sure that Perl 5.10 has the appropriate hooks so that making pluggable regex engines for perl 5.10 and later is easier.


In reply to Re^3: Recursive Regex: Update by demerphq
in thread Recursive Regex: Update by robin

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.