Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!wuarchive!udel!new
From: new@udel.EDU (Darren New)
Newsgroups: comp.lang.c
Subject: Re: #define DEBUG... (using printf for debugging)
Message-ID: <18561@estelle.udel.EDU>
Date: 4 May 90 20:12:27 GMT
References: <11290@hoptoad.uucp> <40628@cornell.UUCP> <7377@crdgw1.crd.ge.com> <1990May4.161910.1353@cs.columbia.edu>
Reply-To: new@ee.udel.edu (Darren New)
Organization: University of Delaware
Lines: 11

>>gordon@mimir.cs.cornell.edu (Jeffrey  Adam Gordon) writes:
>>
>>    I want to have a DEBUG flag which controls whether diagnostic printfs
>>    are executed or not.

I have a version that interactively lets you specify the level of detail
desired, allows part or all to be redirected to the printer or a file,
and so on.   It is somewhat AmigaDOS specific in terms of I/O handling,
but if you can open a separate window on your platform, it shouldn't
be a problem.  If anybody wants it, let me know and I will post it to
someplace appropriate (alt.sources.amiga?)         -- Darren