Sooner or later, you're going to run into an error, whether it's that
you found that a variable is Nil, or that you forgot a variable is
Nil, or any one of the wide range of possible errors, and you're
going to want to do something about it.
So, yes, it is a good idea, and yes, it is possible, but as for the
waste of time, I would suggest just trying things out. Some basic
concepts I've found include that a non-modal message box is a good
idea, and the whole thing becomes more of a waste of time the more
your error system gets its fingers in the rest of your program. If
the interaction between your program and your error reporting is
demanding enough, it can actually detract from your program.
- Andrew Keller
On Dec 3, 2006, at 12:24 AM, RBNUBE wrote:
I might not be thinking about this clearly. Part of what I want to
avoid is
coding MessageDialogs in nearly every single bit of code to handle any
possible error. Usually several in each method.
My thinking was that when an error is encountered that you would
simply
supply an error type and a string to describe the error to a module or
class. This would be done within If/End If and at the end of the
method
using an Exception block. Is this a bad idea? Impossible? Waste
of time?
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
