[fpc-devel] String handling in trunk (was utf8 in 2.6.0)

[Jy V]

> Yes, the exception is probably UTF-8 on Unix systems, but is that really
> worth it to complicate the compiler and RTL? Resourcestings are generally
> not used in performance-critical code, I'd assume. Always using UTF-8 is
> however also fine for me,


I do vote for UTF-8


> btw. I just don't believe it is worth the trouble to support both
> unicodestring and ansistring resourcestrings.
>

I agree.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freepascal.org/pipermail/fpc-devel/attachments/20130105/a0d1ec7c/attachment.html>