Path: utzoo!attcan!uunet!mcsun!unido!mpirbn!p554mve
From: p554mve@mpirbn.UUCP (Michael van Elst)
Newsgroups: comp.sys.amiga.tech
Subject: Re: How do you develop applic
Message-ID: <693@mpirbn.UUCP>
Date: 27 Mar 90 14:37:32 GMT
References: <1294@lpami.wimsey.bc.ca>
Reply-To: p554mve@mpirbn.UUCP (Michael van Elst)
Organization: Max-Planck-Institut fuer Radioastronomie, Bonn
Lines: 34

In article <1294@lpami.wimsey.bc.ca> lphillips@lpami.wimsey.bc.ca (Larry Phillips) writes:
>I just picked up a really nifty little piece of hardware from Black Belt
>Systems.  It's called the 'SoftPanel', and consists of an array of 4 rows of 8
>LEDs, just right for four bytes, two words, or one longword of debugging data,
>or for use as 32 bits of status flags.

I've used some even cheaper method.

try:

#ifdef DEBUG
#define flashcolor(x) { int i; short *p = (short *)0xdff180; \
		for (i=0;i<100000; ++i)  *p = x; }
#else
#define flashcolor(x)
#endif

and flashcolor(...) when you want to show that some piece of code
has been executed.

Lateron, (before I get hands on the ddebug.lib) I wrote
a library that writes messages to some replyport and a real
process dumps them out to a console window.

If you just want to show intermediate results, this is a nice thing,
because you don't need to manage your own output window.
Just 'kprintf(...)' in your program the values you want to show.

The ddebug.lib comes from commodore (like the debug.lib) and allows
printfs to the parallel port (the debug.lib goes to the serial port)
without using PRT or the printer.device.

Michael van Elst
p554mve@mpirbn.mpifr-bonn.mpg.de