EW> Wouldn't
 EW> dbg("function name", ..., "...", ...); 
 EW> be easier? Perhaps even
 
 DM> Heck, no.  That would require writing a dbg function!  Sometimes I
 DM> just need a quick peek, not a full-fledged debugging system.  I'm not
 DM> writing a major software product from scratch, here, I'm adding new
 DM> functionality on to an old product, and need quick peeks into my code.
 CD> 
 CD> Wouldn't TRACE be just what the doctor ordered?????
 DM> I dunno - never heard of it.
 It's a step above that most primitive of debugging tool, the "I
 got here" message.  (Aside: In the olden days, there were no such things 
 as debuggers (at least on the platforms I worked on).  You had to 
 instrument your own code to figure out what went wrong.  One of the 
 handiest of tools was a command that displayed
 "I got to function X" or something similar.)
 Anyway, Windoze compilers (or just the MS flavor?) have a TRACE macro
 (and some others that take parameters) that do the equivalent of the
 "I was here".  The neat thing is that they do it to the "output window"
 when run under the debugger.  They also, like assert() are not 
 included into the release version of the compiled code.
---
 þ Blue Wave/QWK v2.12 þ
---------------