formatting

[sde]

which style do you prefer?

Style 1:

if( var == 1) {

  print("something);

} else {

  print("something else");

}

Style 2:

if( var == 1) 
{

  print("something);

} 
else 
{

  print("something else");

}

i'm mainly talking about the bracket layout here. which style do you prefer?

[alpha]

I said style 1 because that is mainly how I do if/else if/else statements. but for fxns, i use style two. and loops, usually style one. constructors, style two.

[EscapeCharacter]

1 because im lazy and the other way requires you to hit enter one more time

[Epsilon]

#1 because that's just the way I've always done it, which makes it easier for me to read since I'm used to it. And I'm the only one who reads my own code, so I stick with the same style.

[DesertWolf]

Actually I do mine like this:

if( var == 1) {

print("something);
}

else {

print("something else");
}

Kind of a cross between 1 & 2

[redhead]

Style 2, everytime...

[saline]

I've never seen style 2 in my life. Style 1 all the way baby, I give so much space in my code it's like a giant field with little sheep like code snippets grazing about.

When and if I do a final version of anything I'll ususally make it tighter but compilers get rid of white space before they turn it into machine code anyway.

[Valmont]

Check my code in the c++ forums :th: .

[palin]

Definitely style 2 since the editor I use will hide lines between braces and it works better with style 2.

[Travis Dane]

I use style #3.

Style #3 :

 if(var==1)
     print("something");
 else
     print("something else");

[JJoSA]

Never use style 3

Just becase you're allowed to leave off the braces, doesn't mean you should.

It's a bad habit, and will cause you endless headaches when you're trying to figure out why something is working, only to realize that a line of code was executing because it wasn't wrapped in an if statement as thought.

You lose nothing by adding braces, and you gain ease of reading and ease of maintainence

Just Friday I spent hours debugging a piece of code, and one of the main problems was exactly this... a coworker left braces off. Combine that with poor (IE no) indentation in the script and it was damn near impossible to stop

Trust me, I've been doing this 20+ years. Don'e leave the braces off

[joe_bruin]

there is alot more to coding style than mentioned above. luckily, i have a complete .indent.pro file to protect me from your styles.

--braces-after-if-line
--braces-after-struct-decl-line

--cuddle-do-while
--dont-cuddle-else

--indent-level2
--brace-indent0
--case-indentation0
--no-parameter-indentation
--struct-brace-indentation0

--blank-lines-after-declarations
--blank-lines-after-procedures
--leave-optional-blank-lines
--leave-preprocessor-space
--no-space-after-casts
--no-space-after-function-call-names
--no-space-after-parentheses
--no-space-after-for
--no-space-after-if
--no-space-after-while
--space-special-semicolon

--dont-break-function-decl-args
--dont-break-procedure-type

--continue-at-parentheses
--dont-format-comments
--dont-star-comments
--preserve-mtime
--tab-size2
--no-tabs

[Travis Dane]

Originally posted by JJoSA
Never use style 3

Just becase you're allowed to leave off the braces, doesn't mean you should.

It's a bad habit, and will cause you endless headaches when you're trying to figure out why something is working, only to realize that a line of code was executing because it wasn't wrapped in an if statement as thought.

You lose nothing by adding braces, and you gain ease of reading and ease of maintainence

Just Friday I spent hours debugging a piece of code, and one of the main problems was exactly this... a coworker left braces off. Combine that with poor (IE no) indentation in the script and it was damn near impossible to stop

Trust me, I've been doing this 20+ years. Don'e leave the braces off

I have never had the problem of forgetting braces, Never.
Adding braces causes big and ugly code, If you have a problem
with forgetting braces with multiple statements than blame that
and not the braces.

[alpha]

As long as you remember to use braces if you need two or more lines in your if statement; you'll be fine with style 3.

[Cagez]

if($this) {
    that
}

else {
    this
}


loops(conditions)
{
    this
}


function / class
{
    here
}

For me it depends on how much code I'm putting between the curlies. If and else's I always use the same style, but for the others, if I'm only putting three lines, I use Style 1, if I'm putting lots of code, I use Style 2.