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

use Perl Log In

Log In

[ Create a new account ]

Simon (89)

Simon
  simon-use-perl@perlhacker.org
AOL IM: lathosjp (Add Buddy, Send Message)
Busy Man.

Journal of Simon (89)

Tuesday June 11, 2002
07:34 AM

Sick sick sick

[ #5577 ]

Idea of the day: JIT the bytecode produced by the regexp engine. Shouldn't actually be too hard. Produce a bunch of C functions which perform each node, keep everything in registers, and use C magic to build a buffer stringing the assembly code for each function together.


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

Sick sick sick 2 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • ...try this for sick: requiring that a C compiler is available so that a piece of customized regex C code can be compiled into a shared object that will be linked into the Perl executable at startup -- and since regexes can change in runtime, this will happen also during execution.
    • ...try this for sick: requiring that a C compiler is available so that ...

      Isn't that just the Inline principle? Inline::Regex, I can see it now...

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