Copyright (C) 2000-2012 |
Whole document tree
bonobo-exceptionSynopsis
DescriptionThis module contains some useful helper functions that can be used to set various exceptions inside your CORBA methods. It also contains code to map between complex CORBA_Environment exceptions and helpful strings suitable for display to the user. Typically to test for exceptions the BONOBO_EX macro is used thus: Example 1. Bonobo exception trapping and reporting
DetailsBONOBO_EX()
This macro returns TRUE if ev flags an exception. BONOBO_USER_EX()
This macro returns TRUE if ev contains a user exception of type id. BonoboExceptionFn ()
The prototype for user registerable exception decoders. bonobo_return_if_fail()
this macro is used for bonobo preconditons on argument types, usualy inside skels if expr is FALSE a warning is printed and opt_ev is set to ex_Bonobo_BadArg. bonobo_return_val_if_fail()
this macro is used for bonobo preconditons on argument types, usualy inside skels if expr is FALSE a warning is printed and opt_ev is set to ex_Bonobo_BadArg. bonobo_exception_set()
This macro sets the stateless user exception with repo_id on opt_ev or warns if opt_ev == NULL bonobo_exception_get_text ()
Returns a user readable description of the exception. First checks ev against builtin Bonobo exceptions, then falls back to exception names added through bonobo_exception_add_handler_str or bonobo_exception_add_handler_fn. bonobo_exception_add_handler_str ()
This routine adds a simple string mapping for an exception with repository id repo_id, such that when we call bonobo_exception_get_text on an exception of id repo_id we get str back. bonobo_exception_add_handler_fn ()
This routine adds a method mapping for an exception with repository id repo_id, such that when we call bonobo_exception_get_text on an exception of id repo_id the fn is called and passed user_data. When the handler is removed the destroy_fn is called on its user_data. |