Path: utzoo!utgpu!news-server.csri.toronto.edu!torsqnt!tmsoft!masnet!canremote!jonathan.forbes
From: jonathan.forbes@canremote.uucp (JONATHAN FORBES)
Newsgroups: comp.sys.amiga.tech
Subject: Re: How do you develop applic
Message-ID: <90032513573825@masnet.uucp>
Date: 23 Mar 90 07:38:00 GMT
Organization: Canada Remote Systems Limited, Mississauga, ON, Canada
Lines: 24

Well, my development cycle is quite quick, because all my include files 
are in a RAD: disk, which my system boots from.  A software error hardly
ever damages RAD: (in fact, it hasn't happened in several months, now.)
 
For debugging, I use the old fashioned method of using printf()'s at key
points.  Or, if I really don't know what's causing the bug:
 
.. line1 ..
puts("--A--");
.. line2 ..
puts("--B--");
.. line 3..
puts("--C--");
.
.
 
Yes, very very messy, but it's always worked for me (not that I have 
that many GURU-type bugs in my programs.)
 
I've found that printing things at key points is much easier than 
loading up a source level debugger (but then that's just my point of 
view.)
---
 * Via ProDoor 3.1R