[fpc-pascal] Bug in FPC 3.0.0 (was: Bug in FPC 3.0.0?)

[Serguei TARASSOV]

Michael Van Canneyt wrote
> I hope you will send the same mail to embarcadero/Idera. 
> When they added methods to TPoint, they broke have the VCL code ?
> 
> To avoid this, we would need to freeze the code as soon as it is released.

Compared with Unicode migration, introducing the methods into records is not
breaking :)

The code is not frozen but for the core level units the modifications are
rare and very risky without vast codebase and testing.
DB is a vary mature unit, almost all DACs based on it so 100% compatibility
with Delphi does matter.
However, there are some useful methods to extend:
- subclassing (the safest)
- class helpers
- property/method's attributes (need to be introduced at compiler level)
- interfaces (when creating new interface for every extension)

I.e. adding attribute "new" to property/method the compiler will generate
the error when conflicting to resolve names in existing code.

There is no perfect way so why the language extension is the safest
(remember recent discussion about IfThen pseudo-function).
 




-----
--
Regards,
Serguei
--
View this message in context: http://free-pascal-general.1045716.n5.nabble.com/Bug-in-FPC-3-0-0-was-Bug-in-FPC-3-0-0-tp5724274p5724291.html
Sent from the Free Pascal - General mailing list archive at Nabble.com.