use Perl

• Now that gave me a good chuckle! (Score:2, Funny)

  by wickline (135)

  
  Perl 5.12
  
        ...now with Perl Compatible Regular Expressions!
  
  :)
  
  I realize that you're serious, but it's funny anyhow...
  
  -matt
  
• Non default replacement (Score:1)

  by 2shortplanks (968)

  How hard would it be to make a module that caused all regular expressions lexically to use PCRE rather than the default one?
  
  Just a thought. And secondly, what are the benchmarks like?
  • Re:Non default replacement (Score:1)

    by robin (1821)

    How hard would it be to make a module that caused all regular expressions lexically to use PCRE rather than the default one?

    Doing it lexically would be trickier, because you'd have to either add a new set of OPs for the PCRE versions, or at least a flag for the existing ones. I was thinking it would be more along the lines of use re 'debug'; (which is to say, not lexically scoped).

    The first stage is to write a simple XS interface to PCRE, and then we can do some sensible benchmarks as well.
• Named backreferencing. (Score:1)

  by Elthek (2737)

  I really enjoyed the recursive regex page.
  
  You mention:

  The cure for this ill is to allow capturing groups to be named rather than numbered, and to decree that such a name remains in scope until another group is encountered using the same name.

  .. while talking about compositionality. Has anyone looked at implementing this in either the Perl5 engine or PCRE? Is anyone planning to? I'd like to have a crack at it, but it'll probably take a long time and be horrifically messy; though I've studied Kleene Alge

  --
  $a="printf.net"; Chris Ball | chris@void.$a | www.$a | finger: chris@$a
• Implementing re::pcre (Score:2)

  by Simon (89)

  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 goi