Silly thing, but should we stick to a style guide like Google's one?I find that sometimes annoying and maybe we could consider some modifications, but it'd be good to have some homogeneity.

QuoteOriginally posted by: DevonFangsSilly thing, but should we stick to a style guide like Google's one?I find that sometimes annoying and maybe we could consider some modifications, but it'd be good to have some homogeneity.I remember some remarks on this, i.e. it was a wee bit simple-minded and limited. I think it is very difficult to tell people what intra-module style to use. Inter-module interfaces are more important.What about those styles in C, C# ?? I don't think this project should be devoted to C++ style. We are responsible adults. On the other hand your code should be joy to read.

QuoteOriginally posted by: outrunQuoteOriginally posted by: CuchulainnQuoteOriginally posted by: DevonFangsSilly thing, but should we stick to a style guide like Google's one?I find that sometimes annoying and maybe we could consider some modifications, but it'd be good to have some homogeneity.I remember some remarks on this, i.e. it was a wee bit simple-minded and limited. I think it is very difficult to tell people what intra-module style to use. Inter-module interfaces are more important.What about those styles in C, C# ?? I don't think this project should be devoted to C++ style. We are responsible adults. On the other hand your code should be joy to read.We could say "read the google style guide" and feel free to deviateFor the interfaces: boost has naming convenction for directories, header file names, function names, classes, templates. I think we should adopt those.* functions all lower case, no camel case, words separated by underscores.* template parameters start with a Capital(something like this)Yes, that's what I had in mind. Not too strict rules, but some kind of coherence among the parts -- so one can recognize enum's or something.

Agree, no reason to follow the Google style guide (it's over-specified for our purpose, IMHO).No more (perhaps less) than this should suffice: http://www.boost.org/development/requir ... ing"Follow quality programming practices. See, for example, "Effective C++" 2nd Edition, and "More Effective C++", both by Scott Meyers, published by Addison Wesley."// a reasonable summary of "We are responsible adults. On the other hand your code should be joy to read."?