On 15 October 2011 08:27, Dave Abrahams <dave@boostpro.com> wrote:
But I want code to throw so that I don't need to worry and check all details everywhere.
If your code detects a programming error, you need to worry. Yes, it's true that once you say "I'm going to throw under these conditions" it's no longer certain that it's a programming error, but I assert that in this case it remains highly likely. But then the library is no longer allowed to treat it as an error and helpfully do the most appropriate thing for debugging purposes; it has to throw an exception, because it promised to.
It's by no means the most helpful and appropriate thing to, even for debugging purposes. If I want to catch exceptions when thrown, i instruct my environment to do so. But real world errors don't appear under a debugger, they appear on end users machines or on remote server sites and always in release builds. If something doesn't show up in an error log, it didn't happen... I realize I'm standing with another background than most others here, so I simply rest my case. It's been interesting anyways, hope I haven't disturbed too much =)
-- Dave Abrahams BoostPro Computing http://www.boostpro.com
_______________________________________________
Cheers, - Christian