SS>DD| tried.  A new version is out (or should be very soon) with a discount
  >  | if you have already registered one of their C compilers. I prefer the

SS>I can get BC/2 for $195 direct from Borland, but it's only $199 from
  >Indelible Blue.  Some discount, huh?  After I've spent over a thousand
  >dollars for Borland compilers over the years... 

Wait... The upgrade price for v1.5 direct from borland is $79 US, +s/h
+tax.

SS>DD| debugger in CSET++ to that in BCOS/2, both of which cost me about the
  >  | same amount.

SS>I'm almost ashamed to admit it, but I don't use a debugger.  I debug the
  >old-fashioned way, with printf() and strategically placed return()
  >statements. 

Ugh...  I guess that might be a faster way of doing it (the debugger
with BCOS2 1.0 is/was slow!  I'm hoping v1.5 will be faster as my check
went in the mail Friday!

SS>I just haven't had the time or motivation to use a debugger, since most of
  >the errors I have are fairly obvious logic or coding flaws and aren't that
  >subtle.  The only time I ever fire up a debugger and stumble through code
  >is to track down null pointers, since those are to find via the brute
  >force method...

Too True!  But I find that the debugger will throw an answer in my
face...  For example, I'll be thinking one thing, but then when I'm
looking at the list of local variables, I'll see the error in a
different area!  (BTW, I -=NEVER=- used the printf() method... How would
you debug PM?)

Michael Douglass
___
 .Mike's Mail Internet:   MICHAEL.DOUGLASS{at}LCHANCE.SAT.TX.US

--- Maximus/2 2.01wb