jonas.maebe at elis.ugent.be
Tue Nov 22 21:56:47 CET 2016
On 22/11/16 21:46, Maciej Izak wrote:
> 2016-11-22 21:03 GMT+01:00 Jonas Maebe <jonas.maebe at elis.ugent.be
> <mailto:jonas.maebe at elis.ugent.be>>:
> modeswitch prefixedattributes is implemented (and seems it works) and
> can be used by default in Delphi mode only, so I think this is not the
The FPC syntax for procedure attributes is also available in
Delphi-mode, but if the modeswitch is there that's fine.
> b) the generated type info is Delphi-incompatible (TAttributeData vs
> TAttrData, no TAttrEntry). Some people wanted it to be
> Delphi-compatible, other people considered this is an implementation
> detail and that we do not have to follow Delphi here.
> Don't get my next words as attack but... I don't understand double
As I said, some people wanted it to be Delphi compatible, other people
did not mind if it was not. Both categories of people were in the core
team. There is nevertheless in fact a double standard here, but only in
the sense of new features vs. existing features: making something
Delphi-compatible when it is newly introduced does not break anything,
while changing something that already exists breaks backward compatibility.
Exactly because of that reason, the discussions can be more heated when
it concerns a new feature, because it is known that it is virtually
impossible to change later.
More information about the fpc-devel