Re: Updated dataflow semantics for RTT

Sylvain Joyeux <[email protected]> Tue, 22 Sep 2015 14:10:21 -0300
Newsgroups gmane.science.robotics.orocos.devel
Message-ID <CAFENT7+HSv79uz-nqmh-40_XfgEXqVp50YcX7koVNyUY3vJWWA@mail.gmail.com>
> Ahh, I just realized, what is odd about your example. As a design principle,
> a component does not know anything
> about the connections that are attached to the port. So, if you are a robot
> controller and want to always use
> the latest sample, you MUST use R.readNewest(x).
That's the bug. Nobody SHOULD use readNewest, which has been
introduced (by me ...) as a quickfix on top of issues we had.

Connection policy is a system design concern. If one wants to build a
system where the controller should process 10 samples queued in a
buffer, then so be it. Except that readNewest was really made
necessary by the bug Johannes describes.

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