Re: Limitations with v2 port implementation

On Wed, 8 Apr 2015, Sylvain Joyeux wrote:

>> We made a mistake in the original RTT design by providing too many
>> configuration options. This is not a problem if every configuration
>> leads to a unique feature, but it does become a problem if different
>> configurations can provide the same feature. An example is the
>> "difference" between properties and attributes
> Funnily enough, I've made my mind to use properties for setting
> configuration from the system management to the components, and
> attributes to report configuration from the component to the outside
> world.

That usage corresponds to the _opposite_ of the original semantics that
we had in mind 15 years ago. Inspired by the linguistic semantics that a
"property" is something one "has", and an "attribute" is something one
"gets" :-)

Anyway, semantic interpretation of the same mechanism should not be done
inside the library but in the (model-based, application-centric) tools
that make use of it.

> Sylvain

Herman
-- 
Orocos-Dev mailing list
[email protected]
http://lists.mech.kuleuven.be/mailman/listinfo/orocos-dev