Re: [C++ PATCH] P0003R5 - removal of dynamic exception specification from C++17

2016-12-07 Thread Jason Merrill
On Wed, Dec 7, 2016 at 2:00 PM, Jakub Jelinek wrote: > I think throw() is still so commonly used that emitting deprecation warning > for it is undesirable (in any mode). Agreed. > + location_t loc = token->location; > >/* Consume the `throw'. */ >cp_lexer_consume_token (parser->lexer);

Re: [C++ PATCH] P0003R5 - removal of dynamic exception specification from C++17

2016-12-07 Thread Jonathan Wakely
On 07/12/16 20:00 +0100, Jakub Jelinek wrote: Jonathan, there is one hunk in libstdc++ still needed (on top of what you've committed today). Is that ok with you? Yes, sorry I missed that one. Your fix is OK, thanks.

[C++ PATCH] P0003R5 - removal of dynamic exception specification from C++17

2016-12-07 Thread Jakub Jelinek
Hi! This patch attempts to implement the P0003R5 paper (I could find just traces of it in the github repo and the wording in n4618.pdf). I think throw() is still so commonly used that emitting deprecation warning for it is undesirable (in any mode). Bootstrapped/regtested on x86_64-linux and i686