Op Tue, 11 Nov 2008, schreef Luiz Americo Pereira Camara:
Jonas Maebe escreveu:
If people want to rely on what they are used to in non-unicode
environments, then they cannot directly use unicode strings. They'll first
have to assign it or typecast it to a non-unicode string and then operate
on that string. At least if there's any data loss in that case, the
programmer has full responsibility and knows (or should know) the risks.
Just for information Delphi introduces RawByteString type to handle such
case:
http://www.micro-isv.asia/2008/08/using-rawbytestring-effectively/
The string type to use in non-Unicode environment remains
ansistring, which has their system encoding. Rawbytestring is
for strings with unknown encoding, mainly usefull for procedures that work
on any encoding (i.e. seems usefull for copy, insert, delete).
Daniël
_______________________________________________
fpc-devel maillist - [email protected]
http://lists.freepascal.org/mailman/listinfo/fpc-devel
