Richard ONeil wrote:
> I'm not sure that I'm following you here.  Are you saying that you are
> letting the exception crash the app and have the user dictate back
> what was displayed on their screen? Sorry to sound daft, but I just
> ran this by 4 other coders here and they're kinda scratching their
> heads, too.  I really appreciate the dialog, though, because if I'm
> doing something wrong then I need to fix it.  :)

I've been saying that you should never catch an exception if you don't 
know how to handle that specific exception. There is one case when that 
rule doesn't apply, and that's the base exception handler for your 
program -- the last possible place your program could catch the 
exception before it would crash the program. At that point, all your 
program can really do is log the error, show a message to the users so 
they know what's going on, and then close the program. It doesn't really 
matter what the exact type of the exception was since you're going to 
handle them all the same way.

I'm perfectly willing to let a program crash if an exception occurs. I 
will have already caught and handled all the exceptions I know about, so 
anything that manages to reach the very bottom of the call stack is 
necessarily something that I don't know how to recover from. It is 
unwise to allow the program to continue running since I have no idea 
what went wrong. It might have been something trivial, but it might be 
something very important, too. If it were something trivial, then it 
probably shouldn't have warranted an exception in the first place.

When something goes wrong in the program, I'll definitely want to hear 
about it. I'd rather not have the user try to dictate the results to me 
over the phone, of course, so I use something similar to what Delphi 
2005 provides. I have a dialog box that shows a stack trace, plus some 
other pertinent information. It appears in a text box, so the 
information can be copied and pasted into an e-mail message.

Somebody else mentioned MadExcept. It's a great tool. I'd use it, but I 
can't really justify the price right now, and JclDebug provides similar 
functionality with none of the cost.

-- 
Rob


-----------------------------------------------------
Home page: http://groups.yahoo.com/group/delphi-en/
To unsubscribe: [EMAIL PROTECTED] 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/delphi-en/

<*> To unsubscribe from this group, send an email to:
    [EMAIL PROTECTED]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/
 



Reply via email to