Mark-Jason
Dominus wrote a regex-to-text-stream program in ML, and I wrote one in Perl. The process is not terribly difficult, but it can become difficult if allow things like look-ahead and look-behind and deferred-evaluation assertions.
Basically, you must parse a regex into its parts. Then work along these parts, one by one, building a string.
/^\w+\s+(\d{3}|\w+)/
\w+ => "j30_98a3"
\s+ => "\n\n\t \r"
\d{3} => "523"
(or)
\w+ => "j30_98a3"
\s+ => "\n\n\t \r"
\w+ => "r4_QK4"
You basically produce a string by processing the NODE and its QUANTIFIER. I might produce a module to do this in the upcoming rewrite of my regex parser, to appear in the Regexp::Parser hierarchy. Or perhaps Regex::Parser. I don't know.
_____________________________________________________
Jeff[japhy]Pinyan:
Perl,
regex,
and perl
hacker.
s++=END;++y(;-P)}y js++=;shajsj<++y(p-q)}?print:??;
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.