CARMA C++
|
Classes that provide the pecializations of monitor points and sense poiints for different datatypes. More...
Go to the source code of this file.
Classes | |
class | carma::monitor::MonitorPointAbstime |
Absolute time value monitor point. More... | |
class | carma::monitor::MonitorPointBool |
Boolean value monitor point. More... | |
class | carma::monitor::MonitorPointByte |
Byte value (unsigned char) monitor point. More... | |
class | carma::monitor::MonitorPointChar |
Character value monitor point. More... | |
class | carma::monitor::MonitorPointComplex |
Complex value monitor point. More... | |
class | carma::monitor::MonitorPointDouble |
Double value monitor point. More... | |
class | carma::monitor::MonitorPointEnum |
Abstract base class for any enumerated constants, like state machines. More... | |
class | carma::monitor::MonitorPointFloat |
Float value monitor point. More... | |
class | carma::monitor::MonitorPointInt |
Long integer value monitor point (4 bytes). More... | |
class | carma::monitor::MonitorPointReal |
Base class for all real value monitor points (float, double, etc). More... | |
class | carma::monitor::MonitorPointSerialNo |
Serial number monitor point, stored as integer value(4 bytes). More... | |
class | carma::monitor::MonitorPointShort |
Short integer value monitor point (2 bytes). More... | |
class | carma::monitor::MonitorPointString |
String value monitor point (up to 80 characters in length). More... | |
Namespaces | |
module | carma |
IDL for bima Rx Control, inherits from antenna::common::RxControl. | |
carma::monitor | |
Monitor subsystem. | |
Classes that provide the pecializations of monitor points and sense poiints for different datatypes.
These classes all extend from MonitorPoint and provide an additional get/setValue() method. Because the getValue returns different datatypes, we need a class for each one. Templates may have been a more elegant way to solve this problem.
Grouping all these classes together in one file is done because they tend to repeat the same code patterns over and over, with just slight variations because of the datatype. It is easier to maintain all these classes, say add a method, it they are all in one file. I don't like having multiple classes in one file but this seems to be an exceptional case.
$CarmaCopyright$
Definition in file monitorPointSpecializations.h.