> > 1. I don't think we can claim "good" /W4 compile on VS2015, as it even > complains on /W3 (the throwing destructor issue we already discussed) > > We can't change the signature of the dtors due to ABI/versioning requirements in Crypto++ 5.6.3. Its planned for Crypto++ 6.0 when full C++11 support gets cut-in, see https://www.cryptopp.com/wiki/Roadmap.
> > 1. If compiling with /W4 we get a load of C4100s warning about > "unreferenced formal parameters" and some C4505s "unused local variable" > and some "conditional expression is constant" and we get lots of these > warnings. > > OK, I think we should be able to clear some more warnings. > > 1. Linking to Crypto++ yields some issues breaking the ability to use > it. > > More specifically the below demo program lets VS2015's linker fail. > You should use the cryptest program to test the builds. Jeff -- -- 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.
