On Tue, Jul 23, 2002 at 11:08:28PM +0100, Simon Cozens wrote: > [EMAIL PROTECTED] (Nicholas Clark) writes: > > Is there an easy way any regexp internals guru can suggest to patch perl5's > > regexp code to disable the optimiser? > > Benchmarking product X against deliberately-crippled product Y tells you > what, precisely?
It tells you how good the parrot regexp opcode dispatch is relative to the perl regexp opcode dispatch. My understanding is that running a regexp on perl causes it to be first passed to the optimiser, that looks for shortcuts. My understanding is that this is why perl regexps run faster then pcre regexps. Parrot has no optimiser yet. So the current comparison is not fair. We're comparing perl (optimiser + engine) against parrot (engine) I'm suggesting disabling perl's optimiser to get a fairer comparison of the two engines. Nicholas Clark
