[fpc-devel] The (near) future of strings

[Alfred]

Hello,

As happy user of mORMot (ORM framework) and FPC, I am encountering some 
difficulties with the (more or less recent) string changes.
It's hard at the moment to get string handling for Delphi and FPC 
lined-up.

So, I have this (hypothetical) question !

In the (near) future, I am still a very happy user of FPC. And mORMot. 
And sometimes some version of Delphi > XE2.
Lets say its 2017. And I am using FPC 3.2.0. Or FPC 4.0.

What mode will I be using when writing programs/frameworks for both 
Delphi and FPC ?
* is -Mdelphiunicode the way to go ?
* do we have a 100% UTF8 RTL.
* UTF16 / UTF32 ?
* ......

The question could also be: how to make a brand new start that is more 
or less future proof and compatible with Delphi unicode.

The answer to this question is important for making decisions at this 
very right moment.
Some hacks are (still) needed to get strings working for the mORMot 
framework in both Delphi and FPC.
And I (we) would like make hacks that can be dismissed when using future 
versions of FPC.

I know the question is a bit strange, but I would appreciate some 
answers, if possible.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freepascal.org/pipermail/fpc-devel/attachments/20160303/e4c9a131/attachment.html>