Fwd: Naming Conventions

0 views
Skip to first unread message

tom jacobs

unread,
Nov 10, 2006, 6:41:07 AM11/10/06
to bluetu...@googlegroups.com
Sure, that would be good, having some style difference between pri and pub methods. I think we have the underline for private members at swoosh, but its often always done, which is crap. Or done on public members too sometimes.

Ya, I always reckon' braces should match in indentation. I dunno what's up with alister's and lots of other people's opening brace straight after the if( ) etc. I guess it results in less blank lines, but I really like the matching braces having the same indentation.

Oh, and _CLASS_H should be CLASS_H. I don't really like leading underscores, makes it look all weird and system-ey like everything would break if you touch it.

We can put the style up on the wiki, that's what we do at swoosh.

Style is fun.

Tom.

---------- Forwarded message ----------
From: Christopher Ford <christop...@gmail.com >
Date: Nov 9, 2006 10:43 PM
Subject: Re: Naming Conventions
To: tom jacobs <hats...@gmail.com>

I like different cases for public and protected/private members, cos it makes it easy to see which they are at a glance.

I guess that the way you do braces is also technically part of the style (see below). Also ALL_CONSTANTS being named like that.

if
{

}

One very trivial thing. Should it be _CLASS_H or CLASS_H at the top of header files?

Maybe also standardise that all includes and usings should be in one of those comment blocks that makes them easily minimisable? I think you were doing something like that, but I may have broken it when I put the namespace stuff in.

It might make sense eventually to start using Doxygen style commenting, so you can auto-generate man pages for all your classes.

4d


On 11/10/06, tom jacobs < hats...@gmail.com> wrote:
Hm yes, I need to set a style guide (add a text file in /miscellaneous) and then stick to it.

That's the style it is all in at the moment, I think its pretty good... improvements...?

Tom.


On 11/9/06, Christopher Ford <christop...@gmail.com> wrote:
Hey Tom,

You are using camelCase for private and protected members, PascalCase for everything else, including class names etc?

4d



--
Tom.



--
Tom.
Reply all
Reply to author
Forward
0 new messages