On 12/31/05 12:54 AM, "Charles Yeomans" <yeomans .AT. desuetude .DOT com> wrote:
>> As for me, I'd just as soon have Valentina expect one encoding
>> (settable, presumably in the IOEncoding preference) to avoid the
>> overhead of checking with each transaction. With the latest
>> improvements in fc2 I've come to realize that string handling in
>> Valentina is one of the bottlenecks in my app (not the worst one, but
>> it has a noticeable effect on performance).
>
> I don't see how it can be avoided as long as Valentina uses UTF-16 and
> REALbasic uses UTF-8. When support is added for UTF-8 storage, as I
> believe is the case, the overhead of encoding conversion can be
> eliminated.
In fact conversion from UTF8 to UTF16 is only 1% of time as profiler show.
> As for checking encodings, my experience is that checking the encoding
> doesn't cost too much; at the plugin level, it is a function call plus
> integer comparison.
Right.
We will try improve things in this area.
Btw, I believe on lists many times was told that V4RB wait only UTF8 strings
from RB now.
--
Best regards,
Ruslan Zasukhin
VP Engineering and New Technology
Paradigma Software, Inc
Valentina - Joining Worlds of Information
http://www.paradigmasoft.com
[I feel the need: the need for speed]
_______________________________________________
Valentina mailing list
Valentina@lists.macserve.net
http://lists.macserve.net/mailman/listinfo/valentina
©2005 Ruslan Zasukhin |
