News for hackers. Stuff that matters.

A comment on Investigating the Performance Overhead of C++ Exceptions. Parent comment

Re:Investigating the Performance Overhead of C++ Exceptions by boring_twenties on Tuesday February 11, 2020 @04:04PM (#22302829)
Not using them is insufficient, they should be disabled at compile time. IMHO, of course.
[ Parent | on HN ]
Re:Investigating the Performance Overhead of C++ Exceptions by kevin_thibedeau on Tuesday February 11, 2020 @05:08PM (#22303451)
Now what happens when new or STL throws something?
[ Parent | on HN ]
Re:Investigating the Performance Overhead of C++ Exceptions by thedance on Tuesday February 11, 2020 @07:09PM (#22304392)
When you disable exceptions anything that throws calls std::terminate instead. It's actually great.
[ Parent | on HN ]
Re:Investigating the Performance Overhead of C++ Exceptions by pansa2 on Wednesday February 12, 2020 @03:12AM (#22306898)
Is this automatic, or do you need to set it up somehow? `set_new_handler`?
[ Parent | on HN ]
Re:Investigating the Performance Overhead of C++ Exceptions by thedance on Wednesday February 12, 2020 @02:27PM (#22311898)
The standard doesn't give advice about how to break features of the standard, so disabling exceptions is a non-standard feature of the implementation. If you're planning to disable exceptions you'd better read the docs that come with your compiler.
[ Parent | on HN ]