I'm sure there are people who do take this as an invitation to write their own "just cause", but the practical reason for a custom regex engine would be the need to emulate the behavior of some other regex syntax. Bash, PHP, Java, various flavors of the grep command, all have their own slight regular expression nuances.
For example, a person might need to port a large amount of code from PHP to Perl. Rather that study each and every regex in that code, it might make more sense to port the code but leave the original regular expressions in place. Converting syntax is usually fairly straight-forward. Deciphering and converting regular expressions, not always so. You would have that option with a pluggable regex API.
-
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.
|
