On Fri, May 25, 2012 at 12:42 PM, Gabriel Dos Reis <g...@integrable-solutions.net> wrote: > with the current implementation language. Â Consequently, I think > we should retain the binding suggested by the C++ standard. > I realize that the existing GNU C convention says the opposite -- but > then it is written for C.
This point of yours should be stressed. Using writing standards of one language to develop in another language is a fundamentally bad idea. C and C++ kind of look the same, but they are not: http://www.research.att.com/~bs/bs_faq.html#C-slash You wouldn't use the GNU C Coding conventions to write in tcl, and you shouldn't use them to write in C++. You should just create the GNU C++ Coding Standards new, and not base them off of the former. What I see happening in this and in other recent threads is people starting to apply C ideas to C++ code formatting. Aren't there other people out there that already did a pretty good job of painting that shed green? (I'm asking in earnest, I really don't know.) I know in the defense world that the JSF project did a very in depth and very strict standard (http://www.jsf.mil/downloads/down_documentation.htm), but that's as much as I know.
