🚀 go-pugleaf

In article <DEL047.BCD@rivm.nl>, A. van Kessel <imaavk> wrote:
>Take a look at assert.h : assert is a macro with one argument
>Just replace the #include <assert.h> by a
>dummy definition like:
>#define assert(_1) /* _1 */

Yep.  There's a whole can of worms here - I've seen long threads on
this subject in other newsgroups.  But if you want to keep the asserts
in the production code, by all means come up with an alternate macro
definition or some other method to deal with the error.  Unfortunately,
actaully dealing with the inconsistencies on the fly in a robust way
can be extremely difficult.
-- 
Danny Faught -- Convex -- Operating System Demolitions Specialist
"Everything is deeply intertwingled."  (Ted Nelson, _Computer Lib_)