I think I now managed to shave off the speed hit of those special
casing tables quite well,
and all tests still pass (brute force removal of the tables made some
tests of op/lc, op/pat,
and all of uni/* to fall flat on their face), now UTF-8 casing
operations are "only" half
the speed of non-. What basically happened is that every casing
operation created a scalar
and then sprintfed into that scalar and then fetched using that scalar
as a key - and all this
was done even when there was no chance of any of the special casing
rules kicking in.
Duh. I'll test the patch a bit more before sending it to p5p.
--
Jarkko Hietaniemi <[EMAIL PROTECTED]> http://www.iki.fi/jhi/ "There is this
special
biologist word we use for 'stable'. It is 'dead'." -- Jack Cohen
- Re: Converting string to UTF-16LE Nick Ing-Simmons
- Re: Converting string to UTF-16LE SADAHIRO Tomoyuki
- Re: Converting string to UTF-16LE Robert Allerstorfer
- Re: Converting string to UTF-16LE Larry Wall
- Re: Converting string to UTF-16LE Jarkko Hietaniemi
- Re: Converting string to UTF-16L... Jarkko Hietaniemi
- Re: Converting string to UTF-16L... Larry Wall
- Re: Converting string to UTF-16L... Jarkko Hietaniemi
- Re: Converting string to UTF-16LE Jarkko Hietaniemi
- Re: Converting string to UTF-16L... Larry Wall
- Re: Converting string to UTF-16LE Jarkko Hietaniemi
- Re: Converting string to UTF-16LE Larry Wall
- Re: Converting string to UTF-16LE Jarkko Hietaniemi