The recent issue with SecBlock is another PRO reason on the pro/con sheet reason. Also see https://github.com/weidai11/cryptopp/issues/92 .
Visual Studio 2010 and above appears to provide a Code Coverage tool (https://msdn.microsoft.com/en-us/library/dd537628%28v=vs.100%29.aspx). The tool should have pointed out the code paths were untested. Jeff On Saturday, December 26, 2015 at 3:14:13 AM UTC-5, Jeffrey Walton wrote: > > I know some folks have been chomping at the bit for this one... I just > want to make sure we don't have strong objections. > > How do folks feel about making Visual Studio 2010 the default sometime > after the first of the year? "Sometime after the first of the year" would > be a point-release. For example, Crypto++ 5.7, 5.8, 6.0, etc. > > I also want to ensure folks actually *have* a version of Visual Studio > 2010 or above to use. "All they need to do is download the free copy of the > software from the Microsoft website" is a false choice, so please don't > fall into the trap. Here are some of the not-so-apparent reasons and > barriers: ... > -- -- 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.
