Re: contracted exceptions (was Re: Reconsidering assignment)

[Ray Blaak <rAYblaaK@STRIPCAPStelus.net>]

"Martin Krischik" <krischik@users.sourceforge.net> writes:
> Stange - I just used to do (in Java and C++):
> 
>    void doManyThings() throws ManyErrors, SomeError
>     {
>     doSomething();
>     }

Sure. But the problem with this approach is that clients are impacted and need
to have visibility to all of the exception classes, some of which might have
been internal, private to the subsystem's implementation.

Also, this approach is tolerable for one or two exceptions. If you method is
using a lot of libraries, it can get out of hand, and suddenly you need a
throws clause with many exceptions.

An internal change to method bodies can readily cause new exceptions to be
requird, forcing clients to recompile, etc.

It becomes a non-trivial maintenance issue.

-- 
Cheers,                                        The Rhythm is around me,
                                               The Rhythm has control.
Ray Blaak                                      The Rhythm is inside me,
rAYblaaK@STRIPCAPStelus.net                    The Rhythm has my soul.