On 10 Oct 2011, at 22:11, Luiz Americo Pereira Camara wrote:

> 1- Most of LCL must be code page agnostic, so not use UTF8String/AnsiString 
> directly (keep String)

There is no difference between ansistring and string in {$mode delphi} and 
{$mode objfpc}. In a future delphiunicode mode or something like that string 
will be unicodestring, but that's not "code-page agnostic" either. The only 
somewhat code page agnostic string type is RawByteString.

> 2- It should have (dont know if currently has) a compiler switch to change 
> the default code page to UTF8 or whatever, so all variables with type String 
> will map to UTF8String.

I doubt that such a feature will be added. If you want that, declare your own 
string type with whatever default code page you want to use and use that type 
everywhere.


Jonas_______________________________________________
fpc-devel maillist  -  fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel

Reply via email to