Errors

Most Elzed calls return an error code to indicate success or failure. The ones that don't are different because it's syntactically useful for them to return something else, and it's possible to detect an error condition from the returned value (a null where a pointer is expected, for example). Even in these cases, it's possible to get the current error condition with a call to lzGetLastErrorID. To get the text associated with the current error code, call lzGetLastErrorText.

The reliance on error codes was a conscious design choice, and at this point I should make it clear: Elzed does not throw exceptions. Errors that occur inside the library are either handled there, or result in an error code being returned to the caller.

You may identify a function within your code for Elzed to call when an error occurs. See lzSetErrorCallback for more information.

You may define your own error codes. See lzDefineError for details.

About one quarter of the four-dozen built-in error codes have to do with expression parsing; the rest have to do with expression evaluation.

View Elzed errors by error number

View Elzed errors by category