SS> I just haven't had the time or motivation to use a 
 SS> debugger, since most of

There's more motavation for them under os/2...

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

... and that is the reason!  It's also one of the reasons why I started to
abandon DOS when OS/2 1.0 came across my desk.

Bad or NULL pointers jump right out at you under OS/2 (especially under 16
bit os/2).  And rather than creeping up on you long after the offending
code corrupted memory,  you usually find out right away under OS/2 (your
program traps).  When you compile with debug info, and run under a
debugger,  it will take you right to the offending line of code -- where
your bad/null pointer will be staring you right in the face.

Windows NT and most Unix's also have the same benefit.

It makes me REAL nervous to use a DOS/Windows product that does not also
have an OS/2 version.  Knowing that the code has never been run in
protected mode gives me the willies.

Occasionally I still have to write a DOS program (don't tell anyone).  I
always try to develop it under os/2 first,  then port it to dos;  makes me
sleep better.



--- Maximus/2 2.01