Re: C++ coding stds add no value -- discuss!

From:

cpp4ever <n2xssvv.g02gfr12930@ntlworld.com>

Newsgroups:

comp.lang.c++.moderated

Date:

Tue, 17 May 2011 16:40:14 CST

Message-ID:

<6wqAp.5228$2E6.1795@newsfe18.ams2>

On 16/05/11 23:57, Andrew wrote:

<snip>

In the discussion it was not made clear if the stds were to do with
style, layout, naming conventions etc rather than practices to observe
and practices to avoid. Coding stds often mix the two. I am
considering that maybe these colleagues had a point for the first kind
(style etc). Maybe that doesn't add any value. But stds that cover the
2nd category maybe do. In the past when I have been asked to write C++
coding stds I concentrated just on the 2nd category and basically said
"observe the rules in Meyers I, II and III". I couldn't be bothered to
say any more than that because of the herding cats problem and lack of
enforcement but I felt I had to say something because C++ has so many
gotchas. Nowadays if I felt there was going to be no practical
enforcement I wouldn't even bother with quoting the Meyers rules.

Any comments? Do they add value? Why? What kind of stds?

-Andrew Marlow

The major reason, (in no particular order), IMHO for coding standards is
to help provide code that

1 ... Can be more easily understood, (avoid large functions and obfuscation)

2 ... Can be consistently applied to version control, (consistent coding
style)

3 ... Can allow for future development

4 ... Can avoid long compile times, (multiple dependencies)

5 ... Allow for testing during development

6 ... Allow for regular code reviews, (better to catch problems early)

Regards

cpp4ever

--
[ See http://www.gotw.ca/resources/clcm.htm for info about ]
[ comp.lang.c++.moderated. First time posters: Do this! ]