Re: virtual member
On Mar 12, 8:00 pm, Christian Hackl <ha...@sbox.tugraz.at> wrote:
Ron Natalie schrieb:
Christian Hackl wrote:
The FAQ says you should avoid private virtual functions [...]
<URL:http://www.parashift.com/c++-faq-lite/strange-inheritance.html#faq=
-23.4>
The reasoning given in the FAQ is one of the stupidest I've ever seen.
So in your projects you've never personally had the
"confusion" problem it refers to? Not that it sounds very
convincing to me, either... but then again, I've never really
worked on what could be considered a large-scale project in
C++ -- while the author of the FAQ obviously did -- so I
wonder what other experienced developers think about it.
I have worked on large projects. Some very large, in fact (over
150 programmers). We still expected all of the programmers to
be familiar with the standard texts.
The problem is probably less in large projects, because in a
large project, you'll always have one or two experts available
for mentoring, and you'll have written coding guidelines which
explain when and why virtual functions should be private. If
there is a problem, it would be in the small, unorganized
projects where there is a high turn over. But personally, I
don't see it.
--
James Kanze (GABI Software) email:james.kanze@gmail.com
Conseils en informatique orient=E9e objet/
Beratung in objektorientierter Datenverarbeitung
9 place S=E9mard, 78210 St.-Cyr-l'=C9cole, France, +33 (0)1 30 23 00 34