Am 24.07.2015 um 22:59 schrieb Jeffrey Walton: > >> I don't think we should include HKDF and Base64URLEncoder in a >> revision release, so I was going to subtract them manually. They >> can be included in 5.7 or 6.0. > I think dropping HKDF from here is ok, because we /know/ that the > interface will change soon. Concerning the Encoder I'm not too > sure. Generally adding stuff seems to be considered ok for minor > releases (5.6.2 got Keccak) so the encoder may stay. > > > OK. So let me check Crypto++ history and see if there's any precedent. > (There probably is, I just don't recall off the top of my head). > >> Open question: what versions of Visual Studio should be supported? > It would be nice if VS 2005 would be supported but I guess we > don't have to (let it stay untested?). > > > Well, the project files are VS 2008. That ship has sailed. > > > I think VS 2008 should be supported. > > > Yes, definitely. > > Looking to the future, this may change. For Crypto++ 5.7 or 6.0 may > switch to VS2010 or VS2012. We have to be careful how far we leap > forward because those tools are expensive, and I don't want to create > barrier for entry as a Crypto++ user. That is, if an average developer > has VS2010 (but not VS2012 or VS2015), I want them to be able to > download a run with it. I guess upgrading to VS 2010 is probably OK, but we should note that VS2008 is deprecated with 5.6.3 and may not be tested for 5.7.0 / 6.0.0. > > > I also think that VS 2010, VS 2012, VS 2013 and VS 2015 need to be > supported (-> no warnings during compilation at standard W3, 5.6.2 > did this on all supported versions (up to 2012)). > > > Someone else asked about this, so we are going to improve the library > under VS2012 and VS2015 (after the 2008 conversion). > > I have VS2012 and will be getting VS2015 just for this testing. If > someone wants, say, VS2013 tested, then we will need to look at our > options because I am not going to buy both VS2013 and VS2015. I think, if VS 2015 builds fine and VS 2010 and VS 2012 are happy, so will be VS 2013 (if it doesn't have some crazy bug).
I hope you consider / qualify for using VS 2015 (or VS 2013) community edition (professional with some really minor drawbacks and some license restrictions) so this doesn't hurt your wallet too much :) BR JPM > > 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] > <mailto:[email protected]>. > For more options, visit https://groups.google.com/d/optout. -- -- 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.
smime.p7s
Description: S/MIME Cryptographic Signature
