Le 19/01/2019 à 04:35, clipka a écrit :
> Am 18.01.2019 um 21:45 schrieb clipka:
> 
>> should do the trick. Can you do a quick test with that?
> 
> Nevermind.

Yep, it's now working fine (compilation) with gnu, clang and intel
compilers. For me.

I make no provision for other.

*I sleep early this week, saw your messages this morning.

Post a reply to this message

Am 19.01.2019 um 08:59 schrieb Le_Forgeron:
> Le 19/01/2019 à 04:35, clipka a écrit :
>> Am 18.01.2019 um 21:45 schrieb clipka:
>>
>>> should do the trick. Can you do a quick test with that?
>>
>> Nevermind.
> 
> Yep, it's now working fine (compilation) with gnu, clang and intel
> compilers. For me.
> 
> I make no provision for other.

To the best of my knowledge, it should be standard-compliant according 
to C++11 now, and neither C++14 nor C++17 (nor C++20 as it is currently 
planned) should change this.

If you have any indications to believe otherwise, let me know.

Note that we're requiring at least a C++11-compliant compiler by now, so 
there's no need to cater to compilers that don't support `noexcept` and 
would instead require the older `throw()` (deprecated since C++11 and 
removed since C++20).

Post a reply to this message