Activity log for bug #1114137

Date Who What changed Old value New value Message
2013-02-03 08:35:37 Ross Younger bug added bug
2016-07-10 08:33:47 Ross Younger brot2: importance Undecided Low
2016-07-10 08:33:52 Ross Younger brot2: status New Triaged
2016-07-10 08:34:46 Ross Younger brot2: importance Low Wishlist
2016-07-10 08:35:21 Ross Younger brot2: status Triaged Confirmed
2016-07-15 08:30:19 Ross Younger brot2: importance Wishlist Undecided
2016-07-17 03:46:39 Ross Younger brot2: importance Undecided Low
2016-09-03 21:43:05 Ross Younger description Destructors should never throw. The jury is out on whether declaring exception specifiers in general is worthwhile. Should destructors should be nothrow? i.e. virtual ~SomeClass() throw() { ... } Consider using std::nullptr instead of NULL. Destructors should never throw. The jury is out on whether declaring exception specifiers in general is worthwhile. Should destructors should be nothrow? i.e. virtual ~SomeClass() throw() { ... } throw() is deprecated in c++11. Since c++11: void f() noexcept; If an exception propagates from a noexcept function, that's an insta-termination offence. Consider using std::nullptr instead of NULL.
2016-09-04 07:51:08 Ross Younger description Destructors should never throw. The jury is out on whether declaring exception specifiers in general is worthwhile. Should destructors should be nothrow? i.e. virtual ~SomeClass() throw() { ... } throw() is deprecated in c++11. Since c++11: void f() noexcept; If an exception propagates from a noexcept function, that's an insta-termination offence. Consider using std::nullptr instead of NULL. Destructors should never throw. The jury is out on whether declaring exception specifiers in general is worthwhile. Should destructors should be nothrow? i.e. virtual ~SomeClass() throw() { ... } throw() is deprecated in c++11. Since c++11: void f() noexcept; If an exception propagates from a noexcept function, that's an insta-termination offence. Consider using nullptr instead of NULL or 0 constant.