🚀 go-pugleaf

 
Indeed, Mark, debug versions (of frameworks and our own applications - MacApp
and others) should be defensive programmed (which save a lot of time), i use
the following technique taking your example:
 
TFoo::Something()
{...
#if qDebug
   if (!IsObject(aCohandler)) {
     SysBreakStr("TFoo::Something - aCohandler is invalid!");
    return; }
#endif
...
}
 
I prefer to jump into SADE with an own error message (eventually with the
returned OSErr error-code) than wasting my time searching the reason of the
crash which can occur later. I use the same technique before calling Failures
(Failure statement outside the if/endif).
 
SADE must be started up, but i think this is no problem because when working
with MacApp 3.x, we need a lot of meg's (i don't like limited resources! - *The
sky's the limit!*).
 
Of course there are alternatives (jumping into MacsBug, ...).
 
Willy