For more infomation about this bug, visit
Summary: CartesianGeneratorPos, nAxesControllerVel,
nAxesGeneratorPos : reset() method conflicts with RTT
1.4
Product: OCL
Version: trunk
Platform: All
OS/Version: All
Status: NEW
Severity: blocker
Priority: P2
Component: Motion Control
AssignedTo: orocos-dev [..] ...
ReportedBy: peter [dot] soetens [..] ...
CC: orocos-dev [..] ...
Estimated Hours: 0.0

Created an attachment (id=159)
--> (https://svn.fmtc.be/bugzilla/orocos/attachment.cgi?id=159)
Proposal for renaming the reset() methods

The CartesianGeneratorPos, nAxesControllerVel, nAxesGeneratorPos components of
the OCL library have a 'void reset()' method (both in C++ and in scripting)
which conflicts with the proposed RTT 1.4 bool TaskContext::reset() function,
which resets a fatal error. One could rename these methods to avoid future
conflicts.

For the 'Pos' components, it would be renamed to 'resetPosition()' and for the
'Vel' component, to 'resetAll()', as opposed to resetAxis(int).

See the attachment.

I just noticed that a lot of components in the 'applications' directory have or
use a reset() method as well. Maybe it is better to rename TaskContext::reset()
to 'TaskContext::resetError()' ?

Any comments from the application writers/users ?