And I believe that wide-string support should be compile-time option - it would be an overkill to have RE engine with int32 as basic char type, which will be used to handle normal strings (we
have to convert normal strings to wide-strings first then - this
will degrade performance and increase memory usage).
No. Read my proposal again. No need to convert anything. There is a slight binary size overhead, but probably not all that much.
And all strings in pike are wide-strings.
If it's easy to add support for it, why not do it?
/ Per Hedbor ()
Previous text:
2003-01-29 18:42: Subject: Re: Real-life PCRE vs Regexp benchmarking
On Wed, Jan 29, 2003 at 06:10:04PM +0100, Per Hedbor () @ Pike (-) developers forum wrote:
And, also, I really do think that it's best to have int32 as the basic type, perhaps compiled like the lexer, though, with different versions for size_shift 0, 1 and 2. Then you don't loose any performance, and get wide-string support.
We don't have wide-string support in current Regexp anyway, it is even not binary-aware.
And I believe that wide-string support should be compile-time option - it would be an overkill to have RE engine with int32 as basic char type, which will be used to handle normal strings (we have to convert normal strings to wide-strings first then - this will degrade performance and increase memory usage).
Regards, /Al
/ Brevbäraren