On Sun, 29 Dec 2013, Felipe Monteiro de Carvalho wrote:
On Sun, Dec 29, 2013 at 8:15 PM, Graeme Geldenhuys
<[email protected]> wrote:
fpGUI only uses UTF-8 internally, so developers using fpGUI simply use
the functions fpGUI supplies - instead of the FPC RTL ones. eg: use
fpgFindFirst instead of FindFirst. All such functions are the RTL names,
but with a 'fpg' prefix, so makes it easy to remember. They are all in a
single unit too, the fpg_utils.pas unit.
Creating your own set of routines and classes is very easy, but now
comes the real question: From what I understand the new Unicode FPC
will be a one way ticket to the Delphi solution, which means that
TStrings, TComponent, and all other classes will only work with the
new string type.
This is not correct. We'll provide 2 RTLs:
one where string = unicodestring
one where string = ansistring.
This means existing code will function as it used to function if you choose the
second one.
Michael.
--
_______________________________________________
Lazarus mailing list
[email protected]
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
