String performance must be perfect, acceptable is not acceptable ======================== Database servers handle UTF8 efficiently. Also they provide infexing ( hashing for textual data) - these "special tchiniques"...
Again the question, do you think working with current msestring is comfortable? ======================== Yes, very compfortable :) Although UTF8 database setups are comfortable too. Why not utf-16? ======================== With surrogates ? A good replacement for UTF8 provided that all "ansistring" like operations work correctly for surrogates & transparently (no special care) for programming. Though there's a lot of UTF8 contents and there'll be more & more UTF8 contents which will have to be transcoded in run-time from/to to MSE programs if they stay non-UTF8. What is heavier - run-time impact or transcoding one ? ------------------------------------------------------------------------------ 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
