What about the TRegExpr library? <a href="http://www.regexpstudio.com/TRegExpr/TRegExpr.html">http://www.regexpstudio.com/TRegExpr/TRegExpr.html</a><br>The license is MIT-like...<br><br>Cheers,<br>Flávio<br><br><div><span class="gmail_quote">
On 10/31/07, <b class="gmail_sendername">Bee</b> <<a href="mailto:bisma@brawijaya.ac.id">bisma@brawijaya.ac.id</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
> Well, considering that perl's or Python's speed greatly rely on the<br>> underlying C-implementation of (at least) particular functionality, all<br>> those comparisons basically boil down to C vs. C, anyway. Or don't
<br>> they?<br><br>Exactly! That's why I prefer to use fpc own regexpr unit. :)<br><br>-Bee-<br><br>has Bee.ography at:<br><a href="http://beeography.wordpress.com">http://beeography.wordpress.com</a><br><br>_______________________________________________
<br>fpc-pascal maillist  -  <a href="mailto:fpc-pascal@lists.freepascal.org">fpc-pascal@lists.freepascal.org</a><br><a href="http://lists.freepascal.org/mailman/listinfo/fpc-pascal">http://lists.freepascal.org/mailman/listinfo/fpc-pascal
</a><br></blockquote></div><br>