Please try to use something vaguely like these coding standards for patchse and for CRM114 programs.
These aren't absolute rules, but there's a reason for them. Yes, some of the reasons are arbitrary but we at least attempt to rationalize things.
#ifdef THIS_MODULE_DEBUGon a per-module basis, so that CPU-intense checking can be turned on and off on a per-subsystem basis rather than a global
#define DEBUG. * Internal consistency checks - are a good thing. If you can keep the CPU overhead to under 20% or so, then please leave the consistency checks in, even for production / mainline code, and since internal consistency failures will (… at least, should) activate the FAULT/TRAP user-mode error handlers, then the user-mode fault handlers can take over for you. May the email this saves from oblivion make you a rich person. * TRACEing - When deciding between using
user_tracefor things you want the programmer debugging a script to see. Use
internal_tracefor things that would only be of interest to someone debugging the C code. In general, these don't overlap (well, if they do, then
-t -Twill turn them both on so no harm is done either way).