It seems like there would be a significant amount of work required to get Crypto++ into Boost. My attention now is mostly elsewhere, so we'd have to find a volunteer to do the work.
Also, it's not clear to me how much of the existing Crypto++ API would be accepted into Boost, and how much would need to be changed (for violating Boost conventions), or rejected for duplicating existing Boost functionality. How badly would it break backward compatibility for existing applications that use Crypto++? My understanding is that most Boost libraries were designed from the start to fit into Boost, so they don't have this problem. -------------------------------------------------- From: "Zooko O'Whielacronx" <[email protected]> Sent: Monday, May 03, 2010 12:40 PM To: "Crypto++ Users" <[email protected]> Subject: Re: can Crypto++ become Boost.Crypto? > Dear Wei Dai et al.: > > If you do not object, I will do the next step of the process, which is > "use the Boost developers mailing list as a forum to gauge interest a > possible submission". > > Regards, > > Zooko > > -- > 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 "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.
