[fpc-pascal] code example where AnsiString used in FCL (SqlDB) causes data loss

Mattias Gaertner nc-gaertnma at netcologne.de
Wed May 11 22:58:52 CEST 2016


On Wed, 11 May 2016 22:33:13 +0200
Jonas Maebe <jonas.maebe at elis.ugent.be> wrote:

> Graeme Geldenhuys wrote:
> > On 2016-05-11 18:58, Michael Van Canneyt wrote:
> >> >  For 99,99% of cases, no changes to your code are required.
> >> >  If it worked in 2.6.4, it will work in 3.0.0
> >
> > Just curious, so why was there so many changes required for LCL, and a
> > whole wiki page of its own to explain it?
> 
> Those changes were not required, (almost) everything worked still fine 
> with the old code. They made the changes to take advantage of the new 
> functionality in FPC 3.0, because the end result is much simpler code 
> both in the LCL and in user programs.

Yes, simpler and more powerful. For example FPC now supports full UTF-8
in many RTL/FCL functions under Windows.

 
> The wiki page is mainly to explain all of the things you no longer have 
> to do when using this new method.

Yes. And the few incompatibilities.

Mattias



More information about the fpc-pascal mailing list