On Wednesday 06 November 2013 14:27:27 Ivanko B wrote: > Impossible and not wanted. > ============================== > Not a problem with UTF16 as to performance currently since the 2pwr15+ > char check (involving the slow surrogate-handling code) rarely > succeeds on widely-available data. But it definetely and even slowly > should be handled (incl GUI drawing & printing) if such check whenever > succeeds :) Anyway all this can be toggled by compiler options. > BTW it is not 2^15 but >#$d7ff.
Martin ------------------------------------------------------------------------------ November Webinars for C, C++, Fortran Developers Accelerate application performance with scalable programming models. Explore techniques for threading, error checking, porting, and tuning. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk _______________________________________________ mseide-msegui-talk mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
