Gabriel Dos Reis <g...@integrable-solutions.net> writes: > 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.
Er, sure, but that's obviously not an excuse for simply _ignoring_ the existing C standard, as nightstrike seemed to be suggesting. For the most part, the existing C standard (with the obvious generalizations where C++ is a superset) works perfectly fine for C++ too -- and yes, this is still true even if BS is annoyed by some people's use of "C/C++" (I get BS's point, but it's silly to read too much into it). -miles -- We have met the enemy, and he is us. -- Pogo
