On Sunday, April 30, 2017 at 4:27:06 AM UTC-4, olafv...@gmail.com wrote:
>
>
> Op zaterdag 29 april 2017 00:14:15 UTC+2 schreef Jeffrey Walton:
>>
>> I hope I did not conflate the C++17 warning with -std=gnu++17 as default.
>>
>
> I also can't imagine warnings for NULL..
>
> There is "Null pointer constants" but that's something different.
>
Yes, that was part of the problem. Other pieces include Crypto++ using 0 in
some places rather than NULL. Because the 0 was inlined from a header, it
multiplied like feral cats and dogs.
Another piece of the problem is we cannot do the following because GCC
defines NULL (and redefines it). I'm guessing its a bad practice to mess
with the definition of NULL:
#undef NULL
#define NULL nullptr_t
Also see https://github.com/weidai11/cryptopp/commit/5efb019d8bdc593b.
Jeff
--
--
You received this message because you are subscribed to the "Crypto++ Users"
Google Group.
To unsubscribe, send an email to cryptopp-users-unsubscr...@googlegroups.com.
More information about Crypto++ and this group is available at
http://www.cryptopp.com.
---
You received this message because you are subscribed to the Google Groups
"Crypto++ Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to cryptopp-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
