C++ Coding Standards : 101 Rules, Guidelines, and Best Practices

[Stuart Gerchick]

C++ Coding Standards : 101 Rules, Guidelines, and Best Practices by
Herb Sutter, Andrei Alexandrescu is now a month or so away from
release. What is people's opinion on this...is it going to be a
seminal work or lackluster

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

[Mike Wahler]

"Stuart Gerchick" <sg*******@bloo mberg.net> wrote in message
news:e2******** *************** ***@posting.goo gle.com...

C++ Coding Standards : 101 Rules, Guidelines, and Best Practices by
Herb Sutter, Andrei Alexandrescu is now a month or so away from
release. What is people's opinion on this...is it going to be a
seminal work or lackluster

If I were capable of predicting the future, I'd be heading
for Las Vegas or Wall Street. And I can't give an opinion
about the literature itself, since I haven't seen it. However
I suspect it will be of value to many, based upon the reputations
of Herb & Andrei.

-Mike

[Herb Sutter]

On 31 Oct 2004 06:17:29 -0500, sg*******@bloom berg.net (Stuart Gerchick)
wrote:

C++ Coding Standards : 101 Rules, Guidelines, and Best Practices by
Herb Sutter, Andrei Alexandrescu is now a month or so away from
release.

In North America, it should be available in bookstores around now. Andrei
and I got our first copies a week ago, and it was available for sale at
OOPSLA. I haven't looked at my local Barnes & Noble or Borders yet.

More at http://pluralsight.com/blogs/hsutter...0/07/2709.aspx
...

Herb

---
Herb Sutter (www.gotw.ca) (www.pluralsight.com/blogs/hsutter)

Convener, ISO WG21 (C++ standards committee) (www.gotw.ca/iso)
Contributing editor, C/C++ Users Journal (www.gotw.ca/cuj)
Architect, Developer Division, Microsoft (www.gotw.ca/microsoft)

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

[apm]

sg*******@bloom berg.net (Stuart Gerchick) wrote in message
news:<e2******* *************** ****@posting.go ogle.com>...

C++ Coding Standards : 101 Rules, Guidelines, and Best Practices by
Herb Sutter, Andrei Alexandrescu is now a month or so away from
release. What is people's opinion on this...is it going to be a
seminal work or lackluster

Judging from the table of contents, it looks good. It seems to sum up
several pearls of wisdom from sources such as Meyers I, II, III and
GoTW. It looks like it is going to avoid the more contravesial
style-oriented guidelines, and so to me, does not appear to be like
other coding guidelines. I think it is more tutorial in nature and
thus may not be suitable for use by QA during code review. But who
knows, until it is actually published?

Regards,

Andrew Marlow

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

[Stuart Gerchick]

Herb Sutter <hs*****@gotw.c a> wrote in message news:<re******* *************** **********@4ax. com>...

On 31 Oct 2004 06:17:29 -0500, sg*******@bloom berg.net (Stuart Gerchick)
wrote:

>C++ Coding Standards : 101 Rules, Guidelines, and Best Practices by
>Herb Sutter, Andrei Alexandrescu is now a month or so away from
>release.

In North America, it should be available in bookstores around now. Andrei
and I got our first copies a week ago, and it was available for sale at
OOPSLA. I haven't looked at my local Barnes & Noble or Borders yet.

More at http://pluralsight.com/blogs/hsutter...0/07/2709.aspx
..

Herb

I didn't expect Herb Sutter himself to respond to this posting. I am
eagerly awaiting it actually and cant wait to have it in my hands.
Unfortunately, I am in the UK most of the time these days, and will
have to wait a bit for the release. I have it on order and it should
arrive soon.

Thank for for your time Herb. I appreciate it

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

[Stephen Howe]

>What is people's opinion on this...is it going to be a seminal work or
lackluster

With the book not released, how are we supposed to judge? And what do
people's opinions matter, at all, with so little to go on?

Stephen Howe

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

[kanze]

sg*******@bloom berg.net (Stuart Gerchick) wrote in message
news:<e2******* *************** ****@posting.go ogle.com>...

C++ Coding Standards : 101 Rules, Guidelines, and Best Practices by
Herb Sutter, Andrei Alexandrescu is now a month or so away from
release.
At least some of the people I know have seen actual copies of the
printed book. (On the other hand, Amazon says "not yet been released".)
What is people's opinion on this...is it going to be a seminal work or
lackluster

How can anyone tell if they've not actually seen the book. And I'm not
quite sure what you mean by "seminal" -- I wouldn't have considered it
an antonym for lackluster. Given the authors, I expect lots of useful
information, and a readable style. Given the authors, I also expect
some information "just for fun", and some information which won't be
immediately usable because compilers and/or collegues who have to read
and understand the code aren't up to date. On the other hand, by
"seminal", I understand something that will change the way we think
about the language -- a priori, I don't expect either author to present
new ideas that they haven't already discussed here, for example. (In
the industry, from a pratical point of view, "seminal" often means,
"interestin g, but not usable in the next ten years". While some of
Andrei's work might fall into that category -- especially if you have
difficulty getting updates for your collegues:-), for the most part, I
expect that most of the information in the book will be immediately
usable.)

--
James Kanze GABI Software http://www.gabi-soft.fr
Conseils en informatique orientée objet/
Beratung in objektorientier ter Datenverarbeitu ng
9 place Sémard, 78210 St.-Cyr-l'École, France, [phone]

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

[Stuart Gerchick]

"Stephen Howe" <st************ *************** *******@eu.uu.n et> wrote in
message news:<41******* **************@ reading.news.pi pex.net>...

What is people's opinion on this...is it going to be a seminal work or

lackluster

With the book not released, how are we supposed to judge? And what do
people's opinions matter, at all, with so little to go on?

Stephen Howe

As Herb Sutter said above it was available for sale at OOPSLA. People
have now seen it. The kinds of people who are on comp.lang.c++

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

[ma740988]

sg*******@bloom berg.net (Stuart Gerchick) wrote in message news:<e2******* *************** ****@posting.go ogle.com>...

C++ Coding Standards : 101 Rules, Guidelines, and Best Practices by
Herb Sutter, Andrei Alexandrescu is now a month or so away from
release. What is people's opinion on this...is it going to be a
seminal work or lackluster

I approach it from the standpoint that book (my copy showed up
yesterday) - as the title says - is a collection of 'best practices'.

Paragraph 3, page xiii states

" The coding standards introduced by this book are collection of
guidelines for writing high-quality C++ code. They are distilled
conclusions of a rich collective experience of the C++ community.
Much of this body of knowledge has only been available in bits and
pieces spread throughout books, or as word-of-mouth wisdom. This
book's intent is to collect that knowledge into a collection of rules
that is terse, justified, and easy to understand and follow".

The key IMO starts here "This book's intenet .. follow".

Here's one that I'm still confused - if you will - on what constitutes
the ideal implementation approach.

42 per the text. Dont give away your internals

Accessor and mutator as I understand it are - for the most part -
design flaws.
The example in the text shows a GetBuffer member function returing a
char*
In any event, when data needs to be shared among classes this
accessor/mutator beats the alternative (public member data) so I've
never quite understood this one.
A host of get and sets - I suspect - are signs of poor design. I'd
still like to see a concrete example that shows the solution.

My 2cents for what it's worth.

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

[Frank Birbacher]

Hi!

Stuart Gerchick wrote:

People
have now seen it. The kinds of people who are on comp.lang.c++

There are also European people on this newsgroup, like me. And
they don't have the book yet.

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