>>(Please reply to the tutor list, not to me privately)
whoops
>>Generally, you want to catch the exception at the level that knows what to do
>>about it. Your function2() isn't handling the exception in any meaningful
>>sense, it is just converting it to a magic return value. You might as well
(Please reply to the tutor list, not to me privately)
DS wrote:
> Thanks for looking at my problem. Let me try to explain what bothers me
> about raising an error:
>
> Below is a brain-dead example of one function calling another which
> calls another. If in function3 I raise an error, function
DS wrote:
> Hi
>
> Is there any particular standard or approach that I should use for an
> error framework? For example, suppose I have a set of functions that
> call one another, and an error is triggered. I want an error message to
> be passed back to the user, so I could:
Raise an exception,
Hi
Is there any particular standard or approach that I should use for an
error framework? For example, suppose I have a set of functions that
call one another, and an error is triggered. I want an error message to
be passed back to the user, so I could:
1. have an error message passed bac
