> I wonder if I am alone and if I am overdoing it when I use the
> ErrFatalDisplayIf () stuff below. Would most professionals simply go ahead
> w/o any error checking? Is there a gentler way of doing the error checking?
> Simply terminating the procedure would not be an alternative in this case so
> that "if (!myStrH) {return;}" is not acceptable. Adding clean-up code would
> significantly increase the size of the code. Any opinions? Best regards, Paul
do yourself a favour.. dont put it in your release code :)
put a few #ifdef DEBUG around em, so you can pick em up while coding.
also, is it good to give the user a FATAL?? i took out all my
ErrFatalDisplayIf() code and bring up my own dialog.. forcing
the user to reset is bad :)
// az
[EMAIL PROTECTED]
http://www.ardiri.com/ <--- free games!
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
