ab7f1ea0   
   From: moreno_news@mailinator.com   
      
   On 11-11-04 07:26 PM, Castor Nageur wrote:   
   > On 4 nov, 00:51, Pete Becker  wrote:   
   >   
   >> So, when you change these functions to return error codes, your developers   
   will no longer forget to catch exceptions but, instead, will forget to check   
   error codes and the applications will still crash.   
   >   
   > Of course, you are right but my boss asked me to wrap the exception   
   > throwing code so errors are returned and not thrown anymore.   
      
   Huh ...  And here we were all thinking that the actual problem   
   was with the programmers !!!   
      
   -)   
      
   In the messages I'm seeing, I'm surprised that no-one has   
   pointed out that with an uncaught exception, the program   
   *is not really crashing*, but rather exiting.   
      
   With undefined behaviour (such as instances caused by   
   ignoring error codes and continuing like nothing), you   
   may quite likely experience real crashes!   
      
   Not to mention that in many cases (definitely not in   
   safety-critical systems or the like!), it is possible to   
   just put a "master" catch at the appropriate level of   
   the program, and the problem could simply translate into   
   aborting the current document, or the current transaction,   
   etc., and not really exit the whole program;  you can   
   complement this with logging a detailed error that could   
   then help you debug the problem.   
      
   HTH,   
      
   Carlos   
   --   
      
      
         [ See http://www.gotw.ca/resources/clcm.htm for info about ]   
         [ comp.lang.c++.moderated.    First time posters: Do this! ]   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)