What is your programming style with C-like-syntax langauges?

Question

EDIT: I decided this might be better off as a general style thread for C-like-syntax languages (C, C++, Java, ObjC, D)
Everyone, what's the general style you use with languages that have a bracketed syntax like C does?
What are the advantages to your style, as you see it?  For example, K&R style saves vertical file length, but Allman (aka ANSI) makes block starts more clear.
A nice rundown of some common ones here: http://en.wikipedia.org/wiki/Indent_style
And, what is your preferred 'style' when it comes to comments in C?
Do you use the C++-style '//' comments for single lines, or do you still use the C-style '/**/', and why?  Is there anyone that prefers C-style even if they don't care about supporting old non-C99 compilers?
Second, and this is what I'm most curious about, do you often put short comments on the same lines as source code?  How often, and with how much of a space between the comment and the code itself?
When writing comments on the same line as code, do you capitalize the beginning of the comment?  Do you add a period to the end?
Lastly, while we're on the subject, what's your 'rule' for line length?  I like a 100-char limit, but 80-char is the 'standard', and some people use more than 100 due to a rise in large and widescreen monitors.
No holy wars, please!  Just a few questions I've been pondering, it's all personal preference in the end
Last edited by Ranguvar (2009-11-21 01:05:26)

Answer 1

Still my biggest C program (pathetic, I know), this is a solution to K&R's Ch.1 Q.13, which you can read at the beginning of the file.
It's a good example of my current style.
http://repo.or.cz/w/tcpl.git/blob_plain … :/ch1/13.c
I use tabs for indentation, and spaces for aligning code, to allow anyone to set their own tab width.
I like 8-character indent in my editor, though.  The clearly defined blocks really help.
Since the blocks are so clearly defined, I see no need for Allman-style:
if (something)
foo();
bar();
else
bar();
foo();
I use a more K&R style:
if (something) {
foo();
bar();
} else {
foo();
bar();
I use C-style comments for important single-liners and multi-liners, as such:
* IMPORTANT
For single-line comments that are descriptions of a following block of code, I use C++-style comments on their own line, capitalized and with some punctuation except for extremely short comments.
I have no patience for compilers that can't keep up with ISO/ANSI C99 (*cough*MSVC*cough*), which is around 10 years old now, and was publicly in the works long before that
// This next block of code kicks ass.
while (awesomeness) {
kick_ass("awesomeness");
foo();
And for comments that share lines with source code, they are quick lowercase sloppy notes in C-style.  The C-style makes them stand out more and just looks better there, IMO.
No real rule on how far away from the code they are spaced, but usually a 5-char or so minimum, and I often align them with other comments.
super_fuction(1, 2455, "foobar"); /* note to make this understandable, if possible */
Last edited by Ranguvar (2009-11-21 06:50:16)