Set it and respect it in sections of code that are trusted and under your control, and take whatever performance gain you can get. Elsewhere, do it the old fashioned way.
Tex Texin Internationalization Architect, Yahoo! Inc. > -----Original Message----- > From: Andrei Zmievski [mailto:[EMAIL PROTECTED] > Sent: Wednesday, March 08, 2006 12:44 PM > To: Derick Rethans > Cc: php-i18n@lists.php.net; Tex Texin > Subject: Re: [PHP-I18N] Re: surrogates optimization > > > How do we make sure that nothing changes the string contents without > also updating the index of the first surrogate? > > -Andrei > > On Mar 8, 2006, at 11:48 AM, Derick Rethans wrote: > > > On Wed, 8 Mar 2006, Andrei Zmievski wrote: > > > >> Tex, > >> > >> This approach would work only if we allowed access to the string > >> contents > >> always via regimented API. Unfortunately, many third party > extensions > >> (and > >> many bundled ones) simply change the contents of the > string directly > >> via a > >> pointer.. I am not sure we could standardize this. > > > > I think we should seriously consider this though, as it > makes many of > > the string functions quite a bit faster. > > > > Derick > > -- > PHP Unicode & I18N Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > > -- PHP Unicode & I18N Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
