Two commits have been made that addresses the warning and lack of
'noexcept(false)'. Its a very narrow commit. The commits were expedited
because two corporate users listed the warning as a blocking issue.
The first added C++11 feature detection to config.h. The second updated the
preprocessor logic and used noexcept in AlgorithmParameterBase.
*
https://github.com/weidai11/cryptopp/commit/46edae68a5353ee623429ed32db44e37c6a76079
*
https://github.com/weidai11/cryptopp/commit/8e868bf2e542f6286183d0005daccb0466567221
The changes tested OK with and without -std=c++11 on VS2010, VS2012, Clang
3.2, Clang 3.6, MinGW, Cywin, Cygwin-64 and Fedora 22 (i686 and x86_64).
There are still a few open questions. I think the entire strategy needs to
be revisited. Likely, AlgorithmParametersBase will stop throwing, will stop
catching std::excpetion (and friends), it may catch CryptoPP::Exception,
and it will offer a new class method ThrowIfAnyUnused() (or similar). The
user will be responsible for calling ThrowIfAnyUnused() before they destroy
an AlgorithmParameter or the AlgorithmParameter goes out of scope.
Jeff
On Sunday, July 26, 2015 at 7:16:58 PM UTC-4, Jeffrey Walton wrote:
>
> FYI...
>
> I've been trying to run concurrent threads to see where folks are on the
> issue.
>
> We can't change behaviors yet, like not throwing ParameterNotUsed, or
> catching "...". That will be addressed when we can perform a major
> version bump.
>
>
--
--
You received this message because you are subscribed to the "Crypto++ Users"
Google Group.
To unsubscribe, send an email to [email protected].
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
