Re: [Reflex] Adding support for attributes

"Jean-Francois Bastien" <jfbastien_at_cae.com> writes:

> You mean chapter "16.3 Interfaces in Gaudi" in:
> http://lhcb-comp.web.cern.ch/lhcb-comp/Frameworks/Gaudi/Gaudi_v9/GUG/Output/GUG.htm ?

Correct.

The first MS URL you sent talks about using attributes to indicate what features an object of some class has. The example is a class stating it is serializable. This use maps to interfaces well. If the object can be dynamic_cast'ed to an "ISerializable" interface then you know it provides the needed features and you have a way to get them.

> If so, then no, what I'm proposing is completely different: Reflex
> provides introspection reflection on the code's API and interaction
> reflection on this introspection. What I propose is to add
> user-defined attributes to the introspection reflection that's already
> present. It's what's termed as "annotation" in:
> http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1775.pdf

That says the "annotation" is useful to determine, at run time, the length of arrays in order to properly serialize them. ROOT (via rootcint or Reflex) already accomplishes this with the "//[fArraySize]" hint comment.

So, I guess I don't yet see why you need to extend Reflex.

But, anyways, I am just an interested user, not a Reflex developer so I'm not really the one that needs to be convinced....

Regards,
-Brett. Received on Tue Jan 22 2008 - 20:07:56 CET