How would you do your If and else statements

[EwCjE3v7]

I`m trying to adapt to a new style and can`t seem to get it

I used to use

if () {
   ....
} else {
   ....
}

But I`m trying to get used to this type

if ()
{
}

but I don`t know how I should do a else

should I do it like this
1.

if () 
{
   ...
} else 
{
   ...
}

2.

if () 
{
   ....
} 
else 
{
   ...
}

or another way. Thank you

[giblit]

The latter I prefer. Also you still indent after the braces like the first version.

if(something)
{
    dosomething();
}
else
{
    donothing();
}

[EwCjE3v7]

yea forgot that, thank you

I will do that one

[N36fSL3A]

If the if statement runs a single instruction I usually do this:

if(statement)
    runCode();
else
    runThisInstead();

I agree with giblit though, but I like to put a line between the closing bracket and the else statement:

if(something)
{
    dosomething();
}

else
{
    donothing();
}

[MiiNiPaa]

I prefer K&R style (your original style). I use one liners (without braces) only when testing something and prefer to not have them in real code.

My problem with Astyle is that actions are visually separated from condition (braces are thin and easy to overlook). How I see Astyle code at first glance:

if (condition)

    action;

else

    another_action;

[EwCjE3v7]

Yea I`m thinking to maybe sticking to my original style(K&R)

[NoXzema]

if (condition) {
        action;
        action2;
} else {
        action3;
        action4;
}

[giblit]

I might be weird or something but I personally find that version hard to read since the braces don't match up.

[Lowest0ne]

Providing braces reduces the risks of typos if you ever decide to make the statement more complicated.

I personally like words matching words:

if ( /* condition */ (
{
}
else
{
}

[lockandstrike]

I usually do it like so:

if(condition){    
    ....
}
else{
    ....
}

[Mats]

I might be weird or something but I personally find that version hard to read since the braces don't match up.

Me too. I never really understood the K & R approach.

[NoXzema]

Because it uses indentation to indicate the level of nested code instead of brackets.

[N36fSL3A]

NoXzema wrote:

if (condition) {
        action;
        action2;
} else {
        action3;
        action4;
}

Are you a Java programmer?

[TwilightSpectre]

I use the same style, doesn't mean I'm a Java programmer. Though, I myself take it a bit far for some people's liking and go like this:

void func() {
    if (condition) {
        action();
        action2();
    } else {
        action3();
        action4();
    }
}

I guess its a matter of taste. Like how some people prefer putting spaces in between the parentheses and the condition while others don't like spaces at all, or your '*' placement, or your cv-qualifier placement, etc. Personally, I think the only thing that matters is consistency of style.

[Alam]

Multiple conditions can also be used
if ()
{
//code to run
}
else if
{
//code to run
}

[giblit]

Alam wrote:

Multiple conditions can also be used

The topic is more about coding style preferences not what you can do with if/else statements. :P

[BHX]

I do variants.

if (condition1) action1;

else if(condition2) action2;

else action3;

// OR

if(condition){
      action1;
}else{
      action2;
}

// OR
if(condition){
      action1;
}
else{
      action2;
}

// I usually try to use this one when helping with someone else's code
if(condition)
{
      action1;
}
else
{
      action2;
}

[Little Bobby Tables]

Are you a Java programmer?

why would that make him a java programmer

[NoXzema]

Functions are an exception... I actually use I guess what's called "Kernel" style, close to K & F. Functions are declared as such:

int bob(void)
{
        return a_global_int_cuz_bad_programmer;
}

[TwilightSpectre]

@Little Bobby Tables
Different programming languages have different styles that are associated with them. As a general rule, C is assumed to have a coding style like this:

if (something)
{
  dosomething;
}
else
{
  dosomethingelse;
}

While Java traditionally is layed out similar to how my code and @NoXzema's code was layed out. Don't ask me why, I don't actually know.