#include <cexception.h>
Inheritance diagram for cException:

Public Member Functions | |
Constructors, destructor | |
| cException () | |
| cException (int errcode,...) | |
| cException (const char *msg,...) | |
| cException (const cObject *where, int errcode,...) | |
| cException (const cObject *where, const char *msg,...) | |
| virtual | ~cException () |
Getting exception info | |
| int | errorCode () |
| const char * | message () |
| const char * | moduleClassName () |
| const char * | moduleFullPath () |
| int | moduleID () |
Protected Member Functions | |
| void | init (const cObject *obj, int errc, const char *fmt, va_list va) |
|
|
Default constructor.
|
|
||||||||||||
|
Error is identified by an error code, and the message comes from a string table. The error string may expect printf-like arguments (s, d) which also have to be passed to the constructor. |
|
||||||||||||
|
To be called like printf(). The error code is set to eCUSTOM. |
|
||||||||||||||||
|
Error is identified by an error code, and the message comes from a string table. The error string may expect printf-like arguments (s, d) which also have to be passed to the constructor. The 1st arg is the object where the error occurred: its class and object name will be prepended to the message like this: "(cArray)arr". |
|
||||||||||||||||
|
To be called like printf(). The error code is set to eCUSTOM. The 1st arg is the object where the error occurred: its class and object name will be prepended to the message like this: "(cArray)arr". |
|
|
Destructor.
|
|
|
Returns the error code.
|
|
||||||||||||||||||||
|
Helper function for constructors: assembles and stores the message text. If obj is non-NULL, the message text will be prepended (if needed) with the object type and name, like this: "(cArray)array: ..." |
|
|
Returns the text of the error.
|
|
|
Returns the class name (NED type name) of the module where the exception occurred.
|
|
|
Returns the full path of the module where the exception occurred.
|
|
|
Returns the ID of the module where the exception occurred, or -1 if it was not inside a module. The module may not exist any more when the exception is caught (ie. if the exception occurs during network setup, the network is cleaned up immediately). |
1.4.1