On Sat, May 26, 2012 at 10:21 PM, Michael Matz <m...@suse.de> wrote: > Hi, > > On Fri, 25 May 2012, NightStrike wrote: > >> 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. > > That is all nice and fine. For starting from scratch. But we aren't. > We have an existing compiler written in a certain style. We have existing > people actually working on it and used to that style. We don't want to > have a mixture of several different styles in the compiler. I (and I > expect many others) don't want anyone working around the latter by going > over the whole source base and reindent everything. Hence inventing a new > coding standard for GCC-in-C++ (by reusing existing ones or doing > something new) that isn't mostly the same as GCC-in-C isn't going to fly.
if this coding standard is going to be adopted as a GNU coding convention, then you have to be flexible and allow yourself to see beyond the past written in C. You have to ask yourself: how do I want the codebase to look like in 10, 15, 20, 25 years. -- Gaby
