[fpc-devel] Breaking change in FPC 2.6.1

Hans-Peter Diettrich DrDiettrich1 at aol.com
Tue May 1 23:48:59 CEST 2012


Michael Van Canneyt schrieb:

>>> Well, then they'll have to live with the warning.
>>>
>>> And this is the point of having the warning in the first place. Make 
>>> people aware of a coming change.
>>
>> As already mentioned in this thread, a mere hint about "may change 
>> somehow, in the next version" is of no real use. IMO "deprecated" 
>> means to the user that he should change his code *now*, in 
>> anticipation of the coming change. This obviously is not the case with 
>> the breaking change of the bookmark type, where *no* workaround exists 
>> in the current release.
> 
> Instead of repeating the remark, suggesting a solution would be useful.

The solution is so easy: don't mark it as deprecated.

I also have a clear opinion about Delphi compatibility: Every FPC
version must be compatible to a Delphi version. A mix of incompatible
features from different Delphi versions is useless.

Simply specify the Delphi version, to which FPC 2.6.1 should be 
compatible, then the rest is clear.

DoDi





More information about the fpc-devel mailing list