On Monday, December 28, 2015 at 4:19:19 PM UTC-5, jean-pierre.muench wrote: > > Am 28.12.2015 um 09:28 schrieb Jeffrey Walton: > > 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. > > AFAICT this tool is a) only available to the editions above professional > (i.e. Premium and Ultimate for 2010, 2012 and 2013 and Enterprise for 2015) > and b) it only checks code coverage with VS' own Unit Tests (which we don't > use because they don't work well with GCC and such). So I *think* this tool > isn't an option for us. > > We'd need to look into other tools. > Ah, OK. Thanks.
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.
