On Sat, Dec 28, 2013 at 12:46 PM, Michael Van Canneyt <[email protected]> wrote: > > > On Sat, 28 Dec 2013, Marcos Douglas wrote: > >> On Sat, Dec 28, 2013 at 11:11 AM, Michael Van Canneyt >> [...] >> >> So PLEASE, tell us how to make a code on Windows safe, readable and >> strong using FPC 2.6.x (AnsiString) and Lazarus (UTF-8) because I and >> most people still not know. > > > Only use the lazarus UTF-8 functions.
Of course. >>> Yes, 2.8 or 3.0 will be a big change. They will include a unicode RTL >>> somehow. >> >> >> Yes. So, how I can protect my code TODAY to the uncertain future? > > > You can not. > > Who said that this was possible ? Would be if you know how will be the new Unicode implementation, which encoding will be used by default, etc. >>> If you work with 2.6.X, there is no problem to understand the RTL: >>> everything is ansistring: Single byte string, system codepage. >> >> >> I do not have problems to understand that. > > > No, but you do not seem to accept the consequences of this statement. > > Namely: it is NOT possible to use unicode TODAY with the current RTL, > and be future proof at the same time. Right. > When 2.8 arrives, you'll have work to do. We'll try to do as much as > possible to reduce this by offering you a choice. > But you will have work to do, nothing can protect you from this. > > I made the switch from Delphi 7 to Delphi 2010/XE once. This was a huge > task. > > You will just have to try and compile your code with the Unicode RTL, and > fix problems as they pop up. > Or stay in AnsiString and workarounds for UTF-8. Ok, I understand. Thanks. Regards, Marcos Douglas -- _______________________________________________ Lazarus mailing list [email protected] http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
