Re: Data structures

> The sad thing is that it implies a centralized description, that has to
> be shared among every user. We know that maintaining such centralized
> information is a very difficult task.
> Moreover, there's a performance issue since there's often a tradeoff
> between efficiency and generality...

I agree completely. Nevertheless, using common communication mechanisms like
queries, commands etc. which exchange objects allow an easy description of the
interface of a module. Replacing a module simply requires to provide the same
communication object. Adapting own libraries to external formats can easily be
done by deriving another class which provides the needed access method.

For example, one provides an object containing a laser scan. Accessing a foreign
module can be done using the provided laser scan object. Adding own formats at
the client side can be done by deriving a new class from the laser scan object.
This could for example calculate a cartesian scan out of a polar scan ....

Christian


>
>
> _______________________________________________
> Orocos mailing list
> [email protected]
> http://mail.mech.kuleuven.ac.be/mailman/listinfo/orocos

--

---------------------------------------------------------------------
Christian Schlegel
FAW Ulm (Research Institute for Applied Knowledge Processing)
PO Box 2060
D-89010 Ulm
Germany

Tel. : ++49 (731) 501 8949
Fax  : ++49 (731) 501 999
email: [email protected]
WWW  : http://www.faw.uni-ulm.de/
---------------------------------------------------------------------