OverviewAll components should take the form of a class definition file that defines a class derived from one of the component base classes (described below). The name of the class should be exactly the Class Name of the component, with the slashes replaced by underscores, followed by an additional underscore, followed by the release number in numerals. For example, the current numeric data component has class name ClassesThe base classes of all three component types are the same, except that the Process base class has two instances of SystemMLInterface representing its input and output interfaces, as follows. C++ API (1199)
class Data
Symbol eventEventComponentTimeSymbol hComponentComponentOut boutYour derived class must define the virtual
ExtrasIf you #define C++ Source Code (against 1199)
Symbol result EventModuleInitSymbol result EventModuleTermExampleTaken from C++ Source Code (against 1199)
// component information
std/2009/source/numeric"
F_NOT_RATE_CHANGER
brahms-1199.h"
// component class
class COMPONENT_CLASS_CPP Symbol eventEventINT32 dataSymbol COMPONENT_CLASS_CPPEventS_NULLbrahms-1199.h"
|
||
| This is a documentation page for the BRAHMS Modular Execution (Simulation) Framework. For details of licensing and distribution, please click here. To advise of an error or omission, please click here. | ||