Re: JOB:Sr. SW Engineers Wanted-Fortune 500 Co

[Charles Hixson <charleshixsn@earthlink.net>]

I am working on a non-critical project.  Really non-critical:  I'm using Visual
Basic :-(.  But I notice that after I've taken all the valid paths to an if
statement, I throw in an else that 1) throws up an error message dialog and 2)
exits the subroutine.
Now I don't even try to do an error recovery, but I do check for the "Impossible
Error" occurring.  I *think* that so far it's only happened during development.
If not, the users are failing to follow the instructions and call me. (This is an
internal-use project.)

Hyman Rosen wrote:

> kilgallen@eisner.decus.org (Larry Kilgallen) writes:
> > And some small fraction of automobile collision victims who are not wearing
> > safety belts are "thrown clear".  Exceptional cases do get more press.
>
> I am clearly in need of enlightenment, so please explain to me. After
> you have decided that a given situation is impossible, will you
> nevertheless add an error handler for that impossible situation, so
> that if it happens anyway, you can recover gracefully? To what level
> of detail and impossibility will you go? When you write Ada code, how
> many exception handlers for Program Error do you put into your code?