On Monday 05 December 2005 05:13, David Johnson wrote:
> Exactly. Which is why they shouldn't be in libraries. The application
> author shouldn't be compelled to use a language feature he is not
> comfortable with.

Oh please, handling exceptions isn't that hard, and is much less cumbersome
than checking a return code (which has not at all the same use, actually).

> A library function that returns an classic error code
> can be used by both exception and no-exception using applications.

But it you try to handle an error which should be reported by an exception
through a simple return code, you force the programmer into writing some
pseudo-exception handling/stack unwinding code.


>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<