Changes between Version 57 and Version 58 of FAQ


Ignore:
Timestamp:
Sep 11, 2008 11:11:03 AM (11 years ago)
Author:
bennylp
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • FAQ

    v57 v58  
    4242 * assertion must not replace a proper error handling, thus when assertion is disabled, the program should fallback to using error handling as usual. 
    4343 
    44 We use [http://www.pjsip.org/pjlib/docs/html/group__pj__assert.htm#gc98bea768b573f53432076a387864fb3 PJ_ASSERT_RETURN()] macro a lot. The idea of this macro is to raise an assertion during development so that any problems found can be fixed early, and on the production release where assertion is disabled, the macro will revert to error handling so that the application will not terminate unexpectedly with ''Assertion failure'' error. 
     44We use [http://www.pjsip.org/pjlib/docs/html/group__pj__assert.htm#gc98bea768b573f53432076a387864fb3 PJ_ASSERT_RETURN()] macro a lot. The idea of this macro is to raise an assertion during development so that any problems can be found and fixed early, and on the production release where the assertion is disabled, the macro will revert to error handling so that the application will not terminate unexpectedly with ''Assertion failure'' error. 
    4545 
    4646So yes, '''you should disable assertion on the release version''' of the software. This is another convention that we use.