Everything that depends on string being ansistring, like passing strings to cdecl functions (which is done much more often in Lazarus to interface with existing libraries in C).
On Thu, Aug 30, 2012 at 11:39 AM, Hans-Peter Diettrich <[email protected]> wrote: > Michael Schnell schrieb: > >> On 08/29/2012 07:51 PM, Mattias Gaertner wrote: >>> >>> The Lazarus team is glad to announce the release of: >>> Lazarus 1.0 >>> >> Great ! (regarding the excellent work of the Lazarus Team) >> >> But I'll not recommend using it to anybody, as long as there is no final >> decision and implementation on the handling of (Unicode) strings in FPC. >> >> There is a strong tendency to follow the Delphi way and make String to be >> UTF-16 encoded "by default". Supposedly Lazarus will need to follow at some >> point in time and modify all the LCL's user interface functions. > > > How that? What would need to be changed when "string" becomes something > different from AnsiString? > > DoDi > > > > -- > _______________________________________________ > Lazarus mailing list > [email protected] > http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus -- _______________________________________________ Lazarus mailing list [email protected] http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
