[fpc-devel] new string - question on usage

Hans-Peter Diettrich DrDiettrich1 at aol.com
Tue Oct 11 23:20:11 CEST 2011


Marco van de Voort schrieb:
> In our previous episode, Hans-Peter Diettrich said:
>>> components under Lazarus/LCL ecosystem that would need such change. Also 
>>> porting Delphi VCL components would be a lot harder.
>> IMO Lazarus (and FPC) should follow the Delphi way, with strictly 
>> separate Unicode and pre-Unicode versions. Nobody can expect that new 
>> VCL (Unicode) components can be back-ported to Ansi versions.
> 
> Please explain what you mean by "unicode" and what by "ansi" in your
> statement. Without nuancing that, your statement is pretty much meaning
> less.

AFAIR Delphi changed the string type to Unicode (UTF-16) in D2009, i.e. 
D2007 was the last Ansi version.


> And keep in mind that while porting Delphi code is an important factor in
> FPC, but not the only reason.  Many people use FPC for serverside or middle
> tier development.
> 
> It is that why the Delphi model of utf16 strings is not really constructive
> on *nix.

I understand that is annoying when the generic string encoding is ever 
changed into UTF-16. What are the plans with FPC?

DoDi




More information about the fpc-devel mailing list