Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

More recursion 1 Comment More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • This is obviously something I've been thinking about recently. My concerns are mainly to do with what parts of Perl expect various things from the structure of a REGEXP*. For instance, many of the regexp magic variables ($+ and the like) dive into the REGEXP* structure directly. That may not be too much of a problem, since you can use optimize.pm to dike out those GVSVs and replace them with calls to a function in the re::pcre library.

    So other than that, it ought to be pretty plain sailing. If you're going to do it, I'd suggest using the POSIX interface to pcre. Oh, the other thing to think about is what happens to regexp modifiers in toke.c. Your wrapper functions will have to take a Perl REGEXP structure, decode it, feed the arguments into pcre and then decant the results back.

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.