I would suggest the cb (code beautifier) command line arguments as a formal
specification. This way, the coding style can be enforced in an automated
way.
On Friday, November 27, 2015 at 3:01:15 PM UTC-5, jean-pierre.muench wrote:
>
> Hi everyone,
>
> I've read a couple of times when reading the various TrueCrypt reports
> that the TrueCrypt code is quite hard to read, because there's no
> consistent coding style used.
>
> I then thought again and realized that we also lack it.
> Now as we're more open to contributions than before (if I understood
> things correctly) should we define programming style guide lines and add
> them to the project?
>
> BR
>
> JPM
>
> Example (I've never actually seen such a document):
>
> 1) Always use CamelCase and don't use one-letter variable names.
> 2) Follow the specifications (and link them) if using the naming scheme
> for variables of them, like PKCS#1 may use a different notation for the
> different variable than some ISO document.
> 3) Always do for-loops as "for(word64 i=0;i<X;++i)\n{\n ...code...
> \n}\n" with "\n" indicating a newline.
>
--
--
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.
