Orocos Real-Time Toolkit 2.6.0
|typedef boost::function< bool(void)>||Function|
|ConditionFunction (Function impl, bool invert=false)|
|virtual bool||evaluate ()|
|Evaluate the Condition and return the outcome. |
|virtual ConditionFunction *||clone () const|
|The Clone Software Pattern. |
|virtual void||reset ()|
|Some conditions need to be reset at some points. |
|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. |
A functor with the ConditionInterface, for the case where the functor is a bool(void).
|ConditionInterface * RTT::ConditionInterface::copy||(||std::map< const base::DataSourceBase *, base::DataSourceBase * > &||alreadyCloned||)|| const
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.
|virtual bool RTT::scripting::ConditionFunction::evaluate||(||)||
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.