On Donnerstag, 4. September 2008, Arvin Schnell wrote: > What should I do? Open a dialog stating that I coulnd't open a > dialog? Or log an error and abort (what happens already)? > > Any action will just make the code unreadable for almost no > benefit.
If you read back on the archive of this list, those were almost my exact words when this discussion was brought up late last year. In most cases, you can't continue. Game over. And the UI will even post a pop-up (if still possible) with the exact C++ exception text. But still, if there is a reasonable way to continue, or if code is part of a library that can get invalid values from the outside and still react reasonably, the possiblity is there to handle errors gracefully. But in most cases it won't be worth the hassle; something is already broken somewhere. CU -- Stefan Hundhammer <[EMAIL PROTECTED]> Penguin by conviction. YaST2 Development SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Nürnberg, Germany -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
