[fpc-devel] bug report 20473: Please add a directive to define string=utf8string
Felipe Monteiro de Carvalho
felipemonteiro.carvalho at gmail.com
Thu Oct 13 11:02:32 CEST 2011
On Thu, Oct 13, 2011 at 10:47 AM, Marco van de Voort <marcov at stack.nl> wrote:
> But I don't consider this as solution. You have to put each string type in
> the entire libraries on trial, and keep it up.
Could you explain more? Which libraries are you talking about? As I
showed, nothing would need to change in the RTL or FCL classes, they
can use string as usual, or whatever else.
If the problem is in utf8string based libraries, then it only affects
people that use such libraries and authors of such libraries would
take care of solving the issues.
> Moreover, it gets funky when string is banana on Windows and banana2 on
> unix. It keeps working, but if people make mistakes that "happen" to work on
> one platform, the other people might have a problem etc.
That's a general problem of having a string type which varies across
platforms, which is something I was always against.
> Also, dual maintenance of components with Delphi is next to impossible,
> since you would force that scheme also onto them, and all new code first
> needs to be lazarused.
It will not be worse then maintaining Delphi 7 and Unicode Delphi at
the same time, and yet most components support both at the same time.
Plus, isn't Embarcadero pushing FireMonkey anyway?
--
Felipe Monteiro de Carvalho
More information about the fpc-devel
mailing list