9c218f6e   
   From: 0xCDCDCDCD@gmx.at   
      
   On 03.11.2011 19:14, Castor Nageur wrote:   
   > Hi all,   
   >   
   > I am using an API exporting many classes and each class export many   
   > methods.   
   > Each method is throwing some "APIException" exception instance when   
   > something goes wrong.   
   > We are not very happy with this because our developpers use to   
   > forgetting catching the exceptions so many applications crash because   
   > of this.   
   > I can not modify the API (this a third-party API) so my code must not   
   > be intrusive.   
   >   
      
   You might be happier in the medium run investing your time and energy in   
   a proper crash scheme for your application(s).   
      
   That is, make sure all your applications crash properly, producing a   
   usable dump that you can analyse to fix the uncaught exceptions. (Or   
   maybe you could even find a way for a decent top-level exception catch   
   handler, obviating the need to crash in case of an "escaped" API exception.)   
      
   Believe me, I know your problem all too well, but there is really no   
   medium to long term benefit in error masking.   
      
   cheers,   
   Martin   
      
   --   
   I'm here to learn, you know.   
   Just waiting for someone,   
   to jump from the shadows,   
   telling me why I'm wrong.   
      
      
         [ 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)