I think a better alternative might be to attempt to change 'char' to 'int32' in the PCRE-code.
This will not improve performance either :)
Actually, it might. Accessing int32s is typically faster than accessing bytes on modern architectures. Data buses aren't 8bit anymore...
/ Marcus Comstedt (ACROSS) (Hail Ilpalazzo!)
Previous text:
2003-01-29 17:54: Subject: Re: Real-life PCRE vs Regexp benchmarking
On Wed, Jan 29, 2003 at 05:40:06PM +0100, Per Hedbor () @ Pike (-) developers forum wrote:
I think a better alternative might be to attempt to change 'char' to 'int32' in the PCRE-code.
This will not improve performance either :)
But what I found in Pike docs (http://pike.ida.liu.se/generated/manual/modref/ex/predef_3A_3A/Regexp/match....):
"The current implementation (Pike 7.3.51) doesn't support searching in strings containing the NUL character or any wide character."
I guess this is still true for latest Pike. So we lose nothing.
Actually, we can do UTF-8 and binray searching with PCRE - while not with Regexp.
Regards, /Al
/ Brevbäraren