What's your style

[maxib7]

So we all have a personal style guide we adhere to and I was wondering what's your preference concerning brackets?

 

Here's the way I do it

int main (void){    printf("hello, world!\n");    if (/*condition*/)    {        // stuff here    }     else     {        // stuff here    }    return 0;}

However I have seen people do it like this and it drives me crazy when I see it. It's so less legible

int main (void){    printf("hello, world!\n");    if (/*condition*/){         // stuff here    } else {        // stuff here    }        return 0;}

[Casperian]

Snip

I do it the same way you do but I used to do it the other way. I only swapped because some of my functions had like 10+ parameters and moving the brackets down a line helped readability.

[robert1339]

First one for me, well that's how I would type it because I like the organization

[maxib7]

Yeah I hate trying to read other people's code when the brackets are like that. It feels a lot harder to read

[MatthewEnderle]

I do the second format. It just looks so much cleaner and it's much easier for me.

[Guest]

I make sure that my code is as illegible as possible since anyone looking at my code probably can't understand the genius anyway.

[Ciccioo]

I make sure that my code is as illegible as possible since anyone looking at my code probably can't understand the genius anyway.

i like to think that you secretly use PHP for all of your applications, and this comment of yours just made my hypothesis even more realistic

[Guest]

i like to think that you secretly use PHP for all of your applications, and this comment of yours just made my hypothesis even more realistic

 

I program mostly in PHP for my job, so in a way you're right.

[maxib7]

I program mostly in PHP for my job, so in a way you're right.

 

True geniuses only use Lisp 

[as96]

I use the first one.

[Mo5]

The first one. However if there's only 1 line of code to run I sometimes do it like this

if(condition) { /*one line of code*/ }else{//more code}

[Nuluvius]

This has been discussed before.

[DavidTheWin]

First one is objectively clearer

[beingGamer]

first in c#

second in jquery

[MrSuperb]

int main (void){    printf("hello, world!\n");    if (/*condition*/)    {        // stuff here    }    if (/*condition*/)    {        // stuff here    }    else     {        // stuff here    }    return 0;}

int main (void){    printf("hello, world!\n");    if (/*condition*/){         // stuff here    }    if (/*condition*/){         // stuff here    } else {        // stuff here    }        return 0;}

2nd (you might see why)

[cluelessgenius]

i usually let visual studio format my c# code but i do tend to shorten if clauses if possible

string test = condition?"iftrue":"iffalse";

[vorticalbox]

First one

[ManWithBeard1990]

I've used both in the past but I think I mostly use the brackets in their own line.

[Nuluvius]

Every time I have to deal with code that has not been written utilizing Allman style I die a little inside.

[LePawel]

I use bracket styling to separate code by type.

int main(){ //brackets on next line here, shows a function definition, class, namespace etc.  if(/*condition*/){ //but inside a function I condense the code to conserve space.    //stuff here  }  return 0;}

Every time I have to deal with code that has not been written utilizing Allman style I die a little inside.

I don't understand people that follow that sort of stuff. Brackets can easily add 15-20 pointless lines in a complex state-dependent algorithm, stretching it way over single screen height. Same goes for elitists sticking to C stuff like [] arrays in C++11 era.

[Nuluvius]

...

I don't understand people that follow that sort of stuff. Brackets can easily add 15-20 pointless lines in a complex state-dependent algorithm, stretching it way over single screen height. Same goes for elitists sticking to C stuff like [] arrays in C++11 era.

 

And I don't understand people who pile stuff into the smallest possible space at the cost of readability to 'save 15-20 pointless lines' in their opinion.

[DigitalHermit]

/*funciton name *short description or pseudocode *argument 1 - description *argument 2 - description **/int functionname(/*arguments*/){    /*variable declarations and initialization*/    /*descriptions*/    /*code*/    /*more descriptions*/    /*more code*/    subfunction(/*arguments*/){        /*varable declarations and initailization*/                /*descriptions*/        /*code*/        /*more descriptions*/        /*more code*/    }}

I eat up a lot of space with documentation stuff... which I mostly remove once debugging is done...

[Nuluvius]

I eat up a lot of space with documentation stuff... which I mostly remove once debugging is done...

 

In an ideal world there should be very little need for documentation/comments in the code at all.

[MrSuperb]

And I don't understand people who pile stuff into the smallest possible space at the cost of readability to 'save 15-20 pointless lines' in their opinion.

but 1TBS is better readable ?! (especially considering if/else blocks)

[LePawel]

And I don't understand people who pile stuff into the smallest possible space at the cost of readability to 'save 15-20 pointless lines' in their opinion.

If you use spacing/tabbing properly, it makes the shorter versions just as readable as the long one, and if I have to choose between 1 screen height worth of space or 1.5 I'll choose the 1st one, because that can directly impact readability. With constant scrolling to find reference to a variable or name it's much harder to follow the flow.

As I said before, heavily nested state-based functions end up looking like bracketfest, sitting there meaninglessly.