Orocos Real-Time Toolkit
2.6.0
|
This interface represents the concept of a condition which can be evaluated and return true or false. More...
#include <rtt/scripting/ConditionInterface.hpp>
Public Member Functions | |
virtual bool | evaluate ()=0 |
Evaluate the Condition and return the outcome. | |
virtual void | reset () |
Some conditions need to be reset at some points. | |
virtual ConditionInterface * | clone () const =0 |
The Clone Software Pattern. | |
virtual ConditionInterface * | copy (std::map< const base::DataSourceBase *, base::DataSourceBase * > &alreadyCloned) const |
When copying an Orocos program, we want identical internal::DataSource's to be mapped to identical DataSources, in order for the program to work correctly. |
This interface represents the concept of a condition which can be evaluated and return true or false.
Definition at line 58 of file ConditionInterface.hpp.
ConditionInterface * RTT::ConditionInterface::copy | ( | std::map< const base::DataSourceBase *, base::DataSourceBase * > & | alreadyCloned | ) | const [virtual] |
When copying an Orocos program, we want identical internal::DataSource's to be mapped to identical DataSources, in order for the program to work correctly.
This is different from the clone function, where we simply want a new Command that can replace the old one directly.
This function takes a map that maps the old internal::DataSource's onto their new replacements. This way, it is possible to check before cloning a internal::DataSource, whether it has already been copied, and if so, reuse the existing copy.
To keep old source working, the standard implementation of this function simply calls the clone function. If your ConditionInterface uses a internal::DataSource, it is important that you reimplement this function correctly though.
Reimplemented in RTT::scripting::EvalCommandResult, RTT::scripting::TryCommandResult, RTT::scripting::ConditionCache, RTT::scripting::ConditionDSDuration, RTT::scripting::ConditionInvert, RTT::scripting::ConditionCompare< T, compare_op >, RTT::scripting::ConditionBoolDataSource, and RTT::scripting::ConditionBinaryCompositeAND.
Definition at line 50 of file ConditionInterface.cpp.
Referenced by RTT::scripting::ParsedStateMachine::copy(), and RTT::scripting::DataSourceCondition::copy().
virtual bool RTT::scripting::ConditionInterface::evaluate | ( | ) | [pure virtual] |
Evaluate the Condition and return the outcome.
Implemented in RTT::scripting::EvalCommandResult, RTT::scripting::TryCommandResult, RTT::scripting::ConditionFunction, RTT::scripting::ConditionCompare< T, compare_op >, RTT::scripting::ConditionBinaryCompositeAND, RTT::scripting::ConditionExpire, RTT::scripting::ConditionDSDuration, RTT::scripting::ConditionDuration, RTT::scripting::ConditionCache, RTT::scripting::ConditionBoolDataSource, RTT::scripting::ConditionInvert, RTT::scripting::ConditionOnce, RTT::scripting::ConditionBoolProperty, RTT::scripting::ConditionFalse, and RTT::scripting::ConditionTrue.
Referenced by RTT::scripting::EdgeCondition::evaluate(), and RTT::scripting::DataSourceCondition::get().
void RTT::ConditionInterface::reset | ( | ) | [virtual] |
Some conditions need to be reset at some points.
E.g. a scripting::ConditionDuration counts the time since the first time a Command was executed, and if this time exceeds a certain preset time, returns true. Therefore, it needs to be reset, i.e. it needs to start counting, when the command is first executed.. scripting::ConditionOnce has a similar need. This function is called at such times.
Reimplemented in RTT::scripting::ConditionBinaryCompositeAND, RTT::scripting::ConditionExpire, RTT::scripting::ConditionDSDuration, RTT::scripting::ConditionCache, RTT::scripting::ConditionDuration, RTT::scripting::ConditionBoolDataSource, and RTT::scripting::ConditionOnce.
Definition at line 47 of file ConditionInterface.cpp.
Referenced by RTT::scripting::Parser::parseCondition(), RTT::scripting::DataSourceCondition::reset(), and RTT::scripting::EdgeCondition::reset().