Typically people use a style guide to enforce certain style of programming, although I suppose you likely mean style at a higher level, such as OO/procedural, though I suppose that could be enforced as well.
I commonly hear that it is easier to spot good code rather than write it, though that may be a bit different for crypo code. I suppose it is difficult to disagree with the maintainer however. I am sure at least some people would be willing to review code. --JH On Saturday, May 24, 2014 1:44:21 PM UTC-5, Wei Dai wrote: > > The problem with having more contributors is that in order to ensure > security, I'd have to review their code, and it would take just about as > long to review other people's code as to write it from scratch, and that > code would be less maintainable in the long run since it would be in a > different style from my own. An alternative would be to switch to a > different development model with lots of contributors, lots of reviewers, a > lot more resources overall. Unfortunately that doesn't seem very realistic > for Crypto++ given that even OpenSSL has had trouble getting enough > resources to maintain its security in the past. > -- -- 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.
