Exception vs. Return Codes: Mixing and Code Length

Here we go again ... :-)

Triggered by some recent discussion ("Re: Google C++ Style Guide" and
"Re: Exception handling Organization: unknown") I have been thinking
about how I mix exception using code into our non-exception aware code
base. A contrived example can be seen below.

My conclusion would be:
For a given stretch of code: if a newly added piece can fail && if the
operation needs to return a result && if the reason for the error has to
be logged by the calling code -- then the wrap-call-in-try-catch
approach is as good as the if-error-else approach.

Feel free to add your thoughts.

cheers,
Martin

[--code--]
int SomeFunction() {
   using namespace std;

   // 6 Lines
   try {
     CallThrowingOp();
   } catch(exeption const& e) {
     RegisterErrMsg(e.what());
     return ERR_A;
   }

   // 4 Lines
   if(!CallReturnOp()) {
     RegisterErrMsg(GetReturnOpErrMsg());
     return ERR_B;
   }

   double x, y;

   // 6 Lines
   try {
     x = ProcessResult( CallThrowingOp2() ); // ProcessRes = no fail
   } catch(exeption const& e) {
     RegisterErrMsg(e.what());
     return ERR_C;
   }

   // 6 Lines
   long tmp;
   if(!CallReturnOp2(&tmp)) {
     RegisterErrMsg(GetReturnOpErrMsg());
     return ERR_D;
   }
   y = ProcessResult(tmp); // no fail

   // ...
   return NO_ERR_OK;
}
[--/code--]

--
      [ See http://www.gotw.ca/resources/clcm.htm for info about ]
      [ comp.lang.c++.moderated. First time posters: Do this! ]