Discussion on Exception Handling

What does /prog/ think of exception handling, as opposed to other methods such as return values or a global error variable/object? Personally, I think that exceptions in languages like C++ and Java have really introduced a much better method of handling errors that is language-independent. It makes your code infinitely more concise and readable, and now your errors actually have meaning beyond 0, "", null, etc.

I'm in my first year of computer programming at a local university, and we're just learning about exceptions now. It was like the world opened up; I couldn't believe how I could have accomplished anything before this, not knowing about exception handling. Never again will I have to use archaic methods of error handling.

>>16

yeah, one way to get better exception handling in seeples is to create an error handler interface and have various implementation of it, and then you can pass instances of the error handlers down the stack by putting references to them in argument lists. Then when the exceptional situation occurs, the function can call a method in the error handler interface, giving information about the exception to the error handler through the parameter list of its method. And if you find that the error cannot be recovered from like that, then the error handler method can throw a normal seeples exception, and it can be caught somewhere down the stack.