Andy Heninger writes:
> Performance tuning is easier with UTF-16.  You can optimize for
> BMP characters, knowing that surrogate pairs are sufficiently uncommon
> that it's OK for them take a bail-out slow path.  

Sure, but if you are using UTF-16 (or any other multibyte encoding)
you loose the ability to index characters in an array in constant
time. For some applications that isn't desirable.

    -tree

-- 
Tom Emerson                                          Basis Technology Corp.
Sr. Sinostringologist                              http://www.basistech.com
  "Beware the lollipop of mediocrity: lick it once and you suck forever"

Reply via email to