Re: Classes named CFoo (was Re: Odd Exception Behavior)
On 9 Feb, 19:48, Jorgen Grahn <grahn+n...@snipabacken.se> wrote:
On Tue, 2010-02-09, Branimir Maksimovic wrote:
Branimir Maksimovic wrote:
Jorgen Grahn wrote:
On Thu, 2010-02-04, none wrote:
Alf P. Steinbach wrote:
...
* "C"-prefix for a class is a Microsoft-ism, therefore (almost
automatically) ungood.
Guilty as charged. I've been using the "C" prefix since the early
days of Visual Studio.
More generally: I see this class CFoo scheme in a lot of postings
here. Why do people use it, *really*?
I beleive that C is hungarian notation. C stands for "class".
S is for struct, I guess?
I usually don't know or care if my types are structs or classes ...
http://msdn.microsoft.com/en-us/library/aa378932%28VS.85%29.aspx
[Coding Style Conventions]
It seems from that list that the main use of the 'C' is in
COM-infested code, where you don't want to confuse classes
with COM objects of various kinds.
(I hope this is an outdated document. I particularly strongly
dislike the file, class and method documentation headers they
list further down. They're the kind which are guaranteed to
go out of sync with reality, take up lots of screen space, and
yet not say anything worth knowing.)
Note that the document doesn't say you should do it. It just
describes what is done in the samples. And in examples, there
is a (very very small) justification: names like Foo and Bar
don't give the slightest hint as to whether they're a class or a
namespace, for example. (Whereas if you need such prefixes in
production code, you should use better names.)
--
James Kanze