Re: Exceptions, Go to Hell!
On Aug 24, 1:46 pm, "Daniel T." <danie...@earthlink.net> wrote:
thomas <freshtho...@gmail.com> wrote:
Sometimes I found it very convenient to use STL in my application.
But one thing I hate is that STL containers throw exceptions. Because
we handle errors explictly in our application, we don't want
exceptions.
I want to know whether there's any possibility to turn exceptions off,
just like the "new(std::nothrow)" option.
Specifically, will the following operation throw exceptions? How to
handle it without the "try, catch" clause?
-------------
char *p;
string str(p, 20);
-----------
(Don't teach me the benefits of exceptions)
I worked in a shop like that once. We wrote our own string, vector and
map classes that had the same interface as the STL classes (our string
class was cleaner though,) and any situation where the standard class
would have thrown an exception, our classes aborted.
You don't need to go that far though, just treat every situation where
an exception is thrown as a pre-condition violation.
That's quite alright, except that it's not really nice to abort on
bad_alloc in particular. That's almost always too harsh.
It's only OK if the whole program is one "do work" iteration, and even
then, it cost little to write one catch in main(), e.g.
int main()
{
try { return work(); }
catch(const exception& e) // perhaps bad_alloc, perhaps something
else.
{ return error_code_from_exception(); /*nothrow guarantee here*/ }
}
Goran.