[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Best Practices or Design Patterns for Error Handling in KDE
From:       Guillaume Laurent <glaurent () telegraph-road ! org>
Date:       2005-11-07 15:15:15
Message-ID: 436F6F83.1010509 () telegraph-road ! org
[Download RAW message or body]

Sebastian Stein wrote:
> I think the problem is not which technical solution is chosen for error and
> exception handling. If exceptions are used - fine. If return values are used
> - fine too. However, the important point is to do it a) in a unified way and
>  b) capsulate it.
Unfortunately, there isn't any "one true way" of handling errors. Even 
if you have exceptions, in some cases, handling an error through a 
return value is the right way to go (and good luck encapsulating that).

 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]