Does Poco::Exception throw in the copy constructor?

[lskywalker]

I was looking at the Exception source code, and found that it stores the message as a string member in the exception class. This behavior can result in termination of the program according to the C++ standard (15.5.1), since std::string does not guarantee a non-throwing copy constructor. I found a lot of instances in forums and on stackoverflow where this was said to be bad behavior, see e.g. the discussion in http://stackoverflow.com/questions/457020/how-lean-do-my-c-exception-classes-really-need-to-be.

Is this a deliberate decision in Poco? If so, why? std::runtime_error takes care of this problem by using a shared pointer to the string (at least in clang's libc++).

[guenter]

IMO, in practice, the probability of this (the std::string copy constructor throwing due to lack of memory while a thrown exception object is being copied) happening is small enough to not worry about it as a first priority. This could be fixed by storing the string and exception pointer in a RefCountedObject. However, if such a situation happens, all bets are off for most applications anyway.