Reply to thread

Message: [QUOTE="mike3, post: 5026876"] However, this rule seems too strict, as there are places where exceptions really seem like a good idea -- e.g. returning any error from a constructor or overloaded operator. What I'm curious about is just what kind of bad things happen when you use exceptions _wrong_, when you use them where they're _not_ a good fit, and what signs to look for that may indicate you are using them wrong, and an error code would really be better. Or even better, what's the way to do this that does _not_ involve boiling it down to "hard rules". [/QUOTE]