[fpc-devel] Twice stored record RTTI data
Sven Barth
pascaldragon at googlemail.com
Wed Mar 2 19:30:36 CET 2016
Am 02.03.2016 17:49 schrieb "Maciej Izak" <hnb.code at gmail.com>:
>
> 2016-03-02 17:15 GMT+01:00 Sven Barth <pascaldragon at googlemail.com>:
>>
>> This will not be changed due to backwards compatibility. This is not up
for discussion.
>
>
> No. Real argument please and technical detail. You can argue in this way
any buggy element in compiler. Any logical example where this bug "feature"
is used? I think it works in current way by accident. By fixing this bug
more code from Delphi can be ported in correct way, *without functional
workaround*.
>
> If you don't have any logical argument, I'll keep it on Delphi compatible
and logical way in my branch.
>
> it will not break any correctly written code, even more - after fixing
this many correct code from Delphi can start work.
It will break code that relies on non-managed fields being present in the
RTTI. As Jonas said our RTTI is not guaranteed to be Delphi compatible, so
*introducing* Delphi compatibility while *sacrificing* backwards
compatibility (namely to enumerate non-managed fields) is *not* acceptable.
I can already tell you now that this part of your code will definitely not
be merged then.
Regards,
Sven
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freepascal.org/pipermail/fpc-devel/attachments/20160302/d8d2a7c3/attachment.html>
More information about the fpc-devel
mailing list