Rulbus Errors
[Implementation]

---

Detailed Description

This section describes the errors that we categorize as usage, or environmental errors: for example invalid input that is not the result of a programming error.

Such errors that occur in the Rulbus Device Class Library are handled using the try {...} catch( ) {...} exception handling mechanism. If an error occurs, a descendant of RulbusError is thrown that ultimately must be catched in the Rulbus interface function that led to the exception. For example:

 #include "rdcl/rb8510_Dac12.h"

 int main()
 {
    try
    {
       Rulbus::RB8510_Dac12 dac( "mydac" );
       dac.setVoltage( 123 );
    }
    catch( const std::exception& e )
    {
       std::cerr << e;
    }
 }

RulbusError itself descends from std::exception (StdException).

Classes
class	RulbusAddressError
	Rulbus addressing error. More...
class	RulbusCloseError
	Rulbus device close (remove) error. More...
class	RulbusConfigError
	Rulbus configuration file error. More...
class	RulbusContextError
	Rulbus context error. More...
class	RulbusDataError
	Rulbus data error. More...
class	RulbusError
	Rulbus errors base class. More...
class	RulbusHandleError
	Rulbus device handle error. More...
class	RulbusInterfaceError
	Rulbus Interface error. More...
class	RulbusOpenError
	Rulbus device open error. More...
class	RulbusParseError
	configuration file parser error. More...
class	RulbusRangeError
	Rulbus parameter range error. More...
class	RulbusScanError
	configuration file scanner error. More...
class	RulbusTimeoutError
	Rulbus timeout error. More...

---