On 20.09.2014 12:11, Hans-Peter Diettrich wrote:
Sven Barth schrieb:
Am 20.09.2014 01:52 schrieb "Hans-Peter Diettrich" <drdiettri...@aol.com
> It's up to the coder to make all properties etc. published, when he
*intends* to ever use RTTI on them. That't the way to tell the
compiler what to do.
The extended RTTI introduced with Delphi 2010 allows you to even query
private fields if the class developer decided to enable data
generation for that.
AFAIK it works in the opposite direction: the developer must *exclude*
explicitly, in *every* unit, what should *not* be subject to extended
RTTI. That's my strongest point against (Delphi) extended RTTI, while
RTTI by itself is okay for me.
The default values are public and published for methods and properties
and all visibilities for fields.
Regards,
Sven
_______________________________________________
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
