Re: A working document

Herman Bruyninckx <[email protected]>
Newsgroups gmane.science.robotics.orocos.user
Message-ID <Pine.LNX.4.33.0112221643300.8647-100000@pc25-213.mech.kuleuven.ac.be>
On Sat, 22 Dec 2001, Anthony Mallet wrote:

[...]
> What I meant by data is actually the production of other modules (aka
> 'posters' in the current version of GenoM).
> Basically, posters are shared data structures, which are expected to be
> always 'consistent', because every particular poster is produced by a
> _single_ module.
[...]
> Thus posters are (or should be :) 'consistent data structures'. Using the
> data contained within posters can be done thanks to a library which can
> be shared between the producer and the consumer.

This is called a ``monitor'' in the terminology of Software Patterns.

[...]
> I would distinguish 3 class of user:
> . adavanced/application builder (whole system knowledge)
> . module developer (single module knowledge)
> . dummy user (user of the system/modules, and/or developer of other modules)

This subdivision in three makes sense to me.
(``Architect/manufacturer/user''?)

> Only the first type of user  cares about communication mechanisms (setup,
> implementation etc.).
> The second type describes its needs in terms of communication (data
> structures?).
> The third one does not (should not have to) care of communication.

Agreed.

> Codels are written by the second class of user (and that's all what is
> needed to write a module, besides the interface description).

How would you then call the code written by the ``architects'' and the
``users''?

[...]
> Thus there is only one type of codel: it receives data, and structures
> the execution of an algorithm.

So, a codel could not generate data on its own?

Herman
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.