Re: best practice: error handling

["Randy Brukardt" <randy@rrsoftware.com>]

"Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de> wrote in message 
news:1835s5a847r9q$.191jzvxwbypk8.dlg@40tude.net...
...
> BTW, I prefer exceptions to any kind of special values. But as Jeff Carter
> said, there can be gray zones where special values meaning "not so
> exceptional" can be used.

I generally agree. But there are sometimes cases to the contrary. With Claw, 
we originally raised an exception when the Find routine did not find the 
menu entry, window, or whatever it was looking for. But this turned out to 
be a major pain in practice. Moreover, you can make an argument that 
"Not_Found" is not an error per-se; it is a normal result. As such, we 
changed those routines to return a special value (which does not work in 
subsequent operations). It's still possible to mistakenly use that value as 
if it was a valid object, but you'll always get an exception if you do so.

Which just shows that there is no one-size-fits-all solution to this 
problem. There is no substitute for thinking about the problem you are 
solving and how the function is going to be used.

                                 Randy.