Re: Updated dataflow semantics for RTT

> But I do not agree with the analysis that RTT is the best thing to hide
> computations: I have seen way too many control loops implemented with one
> single Orocos component (and activity) per block in a Simulink-like data
> flow... Way too many.

Like ... iTasc ?

Unless you make a system too constrained to be actually useful, there
will always be room to misuse it. That does not spell that the system
itself is bad, only that "best practices" suck (or are inexistent).
This is a neverending fight, but IMO the solution is education, not
some horrible model-based environment too complex to every be used.

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