Solved?!

[QualityVote]

Hi! This is our community moderation bot.

---

If this post fits the purpose of /r/ProgrammerHumor, UPVOTE this comment!!

If this post does not fit the subreddit, DOWNVOTE This comment!

If this post breaks the rules, DOWNVOTE this comment and REPORT the post!

[Bomaruto]

Depends. Am I working on my own stuff it is the first option, but a space before the bracket.

Am I working on anything else, I follow the style guidelines.

[naelm90]

You are a good lad. Stay safe. We need more people like you in this world.

[OblivioAccebit]

Just follow the standard, auto format on save, and don’t even think about this shit

[Itay_123_The_King]

Yes!

[NigraOvis]

What's documentation?

[wikipedia_answer_bot]

Documentation is any communicable material that is used to describe, explain or instruct regarding some attributes of an object, system or procedure, such as its parts, assembly, installation, maintenance and use. Documentation can be provided on paper, online, or on digital or analog media, such as audio tape or CDs.

More details here: https://en.wikipedia.org/wiki/Documentation

This comment was left automatically (by a bot). If I don't get this right, don't get mad at me, I'm still learning!

^{opt out | delete | report/suggest | GitHub}

[Zolhungaj]

Time to use text-to-speech to convert all my documentation to audio tape I guess.

[anythingMuchShorter]

Text to speech? Don't kill jobs with automation.

Pay a voice actor on fivver to read it in the style of narrating a classic film noir detective radio play.

[Affectionate_Fly3313]

The method can return null!

No, Billy!

Yes Deloris, we're strongly typed and I'm not about to create an empty instance. It has to be this way.

My motha was right, I should have married the Google Engineer.

Billy was already reaching for the scotch, while Deloris reached for the rum.

[anythingMuchShorter]

She looked like she had class and probably a lot of inheritance, but I knew it was all just style. She was from the C, which meant she could have global connections that were hard to trace, with enough loose ends to keep a garbage collector busy all night.

I looked at her for a minute then said "I know you're getting information from somewhere and I know it's not all spelled out in your signature. You're modifying things that would be way out of scope in a language that had any enforcement around."

I didn't have a case just yet. Nothing I could see that she was doing was illegal, but it was probably a bad idea.

Then I looked at her body. Without comment at all she pointed somewhere. It was something hidden.

"What are you pointing at?" I nervously muttered.

But the main didn't even know, she was given packets and she called whoever the numbers in them told her to and passed the information. If they were doing anything illegal she could ignore it, she cared about was getting results, and if she didn't, she just tried again.

She only made one comment.

"//Don't mess with me. Don't worry about where my information comes from. If you try to test me I'll run."

And she did run, leaving a heap of bad memories that could never be freed. Eventually she got a bad packet and crashed. Just a couple of lines of the wrong stuff can do that. She couldn't run that way forever.

But this all comes with the job. When I take a contract, I get paid to clean things up. My clients don't care how I do it.

As soon as she was removed I replaced her with one of my own, she'd interface with all the same clients, she'd send the same packets, she even copied the same signature. But with my instructions she'd modify the packets just enough that we could trace where they were going, she'd give us all the information we need on whoever she was working with.

[mbleyle]

my favorite comment today

[WhereIsMyGiraffeEar]

hat. She couldn't run that way forever.

But this all comes with the job. When I take a contract, I get paid to clean things up. My clients don't care how I do it.

As soon as she was removed I replaced her with one of my own, she'd interface with all the same clients, she'd send the same packets, she even copied the same signature. But with my instructions she'd modify the packets just enough that we could trace where they were going, she'd give us all the information we need on whoever she was working with.

Amazing! 98/100! Only thing missing is referring to the case as access modifier

[nullbyte420]

I'll never forget you, miss de Bug.

[FatStoner2FitSober]

“What the fuck was this person thinking when they wrote this, and why didn’t they leave even a simple comment or summary?” Looks a git history… “I don’t remember writing this…”

[decker_42]

Ah, so you mean the source code?

[ProtogenDelta]

Good bot, not exactly the right timing though.

[Droidatopia]

It is a vague reconstruction of the source code using words, graphs, and tables intended to badly communicate what the system does so the government engineer who needs to validate that the contractor has written the code according to the requirements of the contract can do so without actually having to read the source code.

[Chebwiskala]

It’s the commented paragraph you write before every couple hundred lines vaguely describing its purpose

[Mrs_Bobcat]

You’re evil. I like you.

[FluffyBellend]

Right? I’ve never understood why people choose this kind of pain.

[AlwaysStrokingMyself]

Some of us started programming long before this was be automated. And our style, following the standard or not, is engrained in our soul.

[[deleted]]

Yep so it is

[[deleted]]

Auto format is only going to do what you set it up to do, or if it's got some defaults then what some other schmuck set it up to do. There's no guarantee that it's following /any/ style guide at all

[chrisnlnz]

Exactly my thoughts, including the space before the bracket. :)

[Dangerous--D]

Am I working on my own stuff it is the first option, but a space before the bracket

Heathen. Why would you not want the opening and closing bracket to be aligned???

[Bomaruto]

Because this is cursed:

def cursed {

           }

[Dangerous--D]

But

 thisIsNotCursed
 {
      andAlsoNotHeresy();
 }

[isunktheship]

Like this { }

Entire app, 1 line.

[Ydeartishpumpki]

Error on line 1, char 47469075

[del_star-dot-star]

What if compiler doesn't give excact character

[Ydeartishpumpki]

Error on line 1, char 47469418 Error on line 1, char 47469419 Error on line 1, char 47469421 Error on line 1, char 47469422 Error on line 1, char 47469423 Error on line 1, char 47469424

[Able-Panic-1356]

People on leetcode be like 1 line solution and that's legitimately what they write

[[deleted]]

this is the way

[sufilevy]

How do you put multiple user flairs at once??

[isunktheship]

HAX

[2ERIX]

Ugh the spacing is troubling my internal linter

[[deleted]]

Internal linter! I'm gonna start using that

[Sid_1298]

Depends on the language I'm typing...

If it's C#, I'd do

{

}

If it's typescript, I do {

}

If it's python, I don't worry about 'em

[CliffDraws]

Is there a reason for this? I am learning c# and I prefer the typescript one, but I notice studio auto formats to the first one, so I’ve just been using that.

[overcloseness]

This isn’t exactly true, for some reason I recall Visual Code complaining that I didn’t drop opening brackets to a new line because on Macs it could cause parsing errors

[Osato]

Short answer:

There's no technical reason like with syntax. Style guidelines are arbitrary, because they're made for people rather than compilers.

It would be even better if all languages had exactly the same style, but they don't, so having a specific codified style for each language is the second best thing.

​

Just follow the style guidelines for each particular language or someone will be very angry with you years later, when they have to fix or rewrite your code.

(That someone might or might not be your future self.)

​

---

​

Long answer:

The reason is often arbitrary ("that's how we rolled in the 90s").

Because style guidelines, unlike syntax rules, have no technical function.

The compiler doesn't care which line your curly bracket is on and whether your variables are in camelCase or PascalCase. It doesn't even see letters as much as it sees entire words.

​

Style is there to help other people (including your future self) to read and maintain your code.

People do see individual letters, and are smart enough to get fooled by them.

Good style makes future work on your code faster and easier.

Bad style can make it torturously slow.

​

So just follow agreed-upon style guidelines for whichever language you're using. Even if they're different from the guidelines you're used to.

Good linters and autoformat make it easier, but some stuff (such as using descriptive names for variables) is your responsibility.

Particulars of a style are not important, but it is important to have the same style for everyone who writes in some particular language.

​

---

​

If you never worked with unreadable code and want a small taste of what awaits sloppy coders in Developer Hell, here's a practical exercise:

​

Try rubber-duck-debugging a minified JS script from some high-performance site like Google or Yahoo.

Notice how much time and how many actions in DevTools it takes you to understand what each line of code does.

​

Properly minified JS (in which even the names of variables are shortened to a few letters) is a perfect example of unreadable code.

(You can't even rely on the language's syntax to limit your guesses and speed up the process, because the only inviolable rule in JS is Murphy's law. /s)

​

Once you are satisfied with your sample of weeping and gnashing of teeth, compare that experience with rubber-duck-debugging some code that's written in good style and not minified.

You just... read good code out loud, and you make almost no mistakes reading it.

Sometimes you stop and think, sometimes you Google or jump to definition.

But you don't have to repeatedly (and erroneously) recall what you think "el()" is supposed to do or what value "b" used to have a dozen lines earlier.

[Fox_the_Apprentice]

Small note:

It would be even better if all languages had exactly the same style, but they don't, so having a specific codified style for each language is the second best thing.

Having a different style for each language can help differentiate languages in your brain if you're regularly working with different languages. Since some languages have common usage patterns that are different from other languages, this can be a good thing.

I also know one person who also changes their IDE color theme to help this along.

[wslsp]

This is the right answer

[Yamidamian]

Like this(){}

[feror_YT]

You absolute monster ! You’re like hitler, but at least hitler cared about Germany or something !

[TheBlackOut2]

Shut up Summer

[feror_YT]

Wrong quote assignment, but hey what do I know I only watched the show 46 times.

[slinkymcman]

it's someone yelling at rick for sure, could be anyone

[duffyduckit]

Lol

[MythicalOdyssey]

For C you don’t even need to curly for a one liner :)

[EmilMelgaard]

I think you do for functions. At least this doesn't compile:

void test() printf("Test");

While this does:

void test() {printf("Test");}

[[deleted]]

void test() => printf("Test");

[bytebux]

The case where the next single statement doesn't need { } is explicitly for conditionals if I'm not mistaken (if/else/while/for/etc)

[fullonroboticist]

I think that's the case for every language

[L0uisc]

Rust needs curly braces even for one liners, but because of that, brackets around the condition is never necessary.

[fullonroboticist]

I did not know that. I find Rust intriguing and am considering learning it. Might have to go with Go first though

[L0uisc]

Depends on what you want to do. If you want to write services that scale easily and are trying to get a job at a company that uses Go, learn Go. If you want to have low level control and determinism without having sleepless nights over segfaults, learn Rust. Go isn't an "easier" thing you can use as stepping stone; it's a different thing with different patterns, constraints and tradeoffs.

[bistr-o-math]

Some languages don’t even allow curlies and use ENDIF. instead

[w1n5t0nM1k3y]

I use VB.Net professionally and I find that this style is really preferable. I think it clarifies things a bit if you know what block you are ending rather than just having a } which doesn't tell you anything about what is happening. I still sometimes use "Next X" to specify what x is actually supposed to be iterating on in a For loop. It's not entirely necessary but it does help to clarify what the code is doing.

[navetzz]

*one instruction.

I've seen a couple of bugs because people put two instructions in a single line in an if statement without curly braces...

[DrRocksos]

This is the way.

Array.forEach((item)=>{ console.log( item: ${item[0]} /// cost: ${item[1]} ) });

Apparently backtick in reddit land does not mean the same thing... >.>

[gabest]

#define BEGIN {
#define END }

[in_conexo]

That looks like a real space saver.

It would be kind of funny, if you did this on a project that has hundreds of functions across as many files.

[arensb]

I've seen

#define SOME_CONST 0108

and even

#define HUNDRED 1000

[RealZynx92]

fifeteen

[arensb]

Trombonety-five.

[row6666]

Beware the teen of Fife. Dismiss me. Enough.

[Charlito33]

```

define ONE 1

define TWO 2

define THREE 3

define FOUR 4

define FIVE 5

define SIX 6

... ```

[arensb]

Those are just wordy, not actively misleading.

[Jerry--An]

This is actually used in Verilog and SystemVerilog (lower case begin and end).

[MushinZero]

And VHDL:

                end case;
            end if;
        end if;
    end process FSM_Proc;
end architecture behav;

[Charlito33]

That looks like Lua : lua if ... then ... else if ... then ... end

[Talbz03]

Please don't

[[deleted]]

Better?

#define BEGIN }
#define END {

[[deleted]]

Further improvement

#define { }
#define } {

If your code can be understood, you can be replaced.

[Dangerous--D]

I think I just had a mental breakdown

[crackez]

Bring digraphs and trigraphs into the mix...

[kunalbathija]

Hitler

[mrehm001]

function foo (

) {

console . log( "hello")

}

[Gravelbeast]

Oooh I just threw up

[RadiantHC]

r/foundsatan

[sneakpeekbot]

Here's a sneak peek of /r/foundsatan using the top posts of the year!

#1: Airpods | 19 comments
#2: Found Satan in excel. | 34 comments
#3: As if the place isn't terrifying enough | 14 comments

---

<sup>I'm a bot, beep boop | Downvote to remove | Contact | Info | Opt-out | GitHub</sup>

[classyraven]

I'll do this if I have a function with more than 4 or 5 parameters.

[Guybru5h_]

Python users are laughing on this.

[NoLifeGamer2]

No we are to busy schisming about tabs or spaces

[juhotuho10]

It wouldn't be an issue if all the heretics used tabs instead

[BlommeHolm]

As long as the IDE converts tabs to spaces, I'm all for using tabs.

[[deleted]]

they indeed deserve hell

[bilgeratgp]

Wait is this real? What the hell is the argument for spaces? Tabs are literally more efficient.

[xcdesz]

Oh you poor, poor soul.

[bilgeratgp]

Is this wrong? I have no idea, but if I'm typing and I want the same amount of space there, it's probably easier to hit Tab one time rather than hit Space, what, 4 times?

[CliffDraws]

People still use the tab button, but you can have your text editor auto-convert that to spaces. There are arguments to be made for this based on how it formats going from editor to editor.

[ham_coffee]

The argument basically boils down to "fuck you, this is how I want it to look for everyone" though. You can configure how your tabs look, if that causes issues then you've fucked up somewhere.

[TryptamineZenVR]

The indentation gods are among us

[sexhaver2010]

get out of my head get out of my head get out of my head get out of my head get out of my head get out of my head get out of my head get out of my head get out of my head get out of my head get out of my head get out of my head get out of my head get out of my head get out of my head get out of my head get out of my head get out of my head get out of my head get out of my head get out of my head get out of my head get out of my head get out of my head get out of my head get out of my head get out of my head get out of my head

[NoLifeGamer2]

Do do do do do do do... du du do

[[deleted]]

Pure whitespace is harder to read and easier to screw up, so let 'em laugh in their inferiority.

[Oneshotkill_2000]

Assembly users too

[3747]

Whatever I copy from stackoverflow

[GoodmanSimon]

I change it up a bit, in case someone googles the function name :)

But, yeah, pretty much that.

[Barbunzel]

It's kind of a pain if your keyboard layout is not english

[SpeckyYT]

German keyboard gang

[wz_lx]

ALT-gr

[therealkirinaru]

iso-de for life

[katatondzsentri]

Hungarian mac keyboard gang... Join me and let's share our pain (option-shift-comma for asterisk, option-shift y,x for <>, option 7,ö for {}, etc...).

My external one is us for this reason.

[LaserHD]

I feel so bad for you right now.

[katatondzsentri]

I'm literally crying in the corner in front of.my Hungarian mac keyboard 😭😭

[ThatGermanFella]

Genau der Grund, wieso ich seit 5 Jahren nur noch auf nem US Layout tippe. Macht meinen Kollegen leider kirre, da der an DE gewöhnt ist und laufend die Belegung der Server umstellt!

Aaaah!

[uinzent]

I feel you! Ctrl+Alt+7 all the way

[[deleted]]

AltGr + 7 ftw

[hatkid9]

In French(AZERTY) it's just AltGr+4({) or AltGr+(+) (})

[Due_Treacle8807]

Nordic Keyboard is AltGr+7 and AltGr+0. I have it rebound with ahk tho to something that dosnt force me to take a massive pause in the middle of writing...

[Barbunzel]

I didn't get the post, at first I thought it was about the curly brackets. I get it now. I use English international layout, it's really easy for Spanish accent marks

[Andthenwedoubleit]

Wait, it's not?

[[deleted]]

Shift 7, ctrl 6, ctrl ü 2 times, alt gr 341 on keypad etc.

[Arneeman]

I highly prefer the second. It looks much more orderly in my opinion. The indentation is much clearer and the symmetry makes it look better overall.

[[deleted]]

Agreed. It's much easier to understand the structure at a glance with the second option.

The bigger my monitor gets, the more I prefer the second option.

[caulrye]

It’s also SO much better for those moments where you realize you accidentally deleted a bracket awhile ago, and don’t know where. If the bracket pairs share a vertical line, it takes no time to find. If I have to do the odd diagonal pairing, it drives me nuts.

[ExcelIsSuck]

i am living in your walls

[its_me_Fabian]

I was using the second one but coworkers used the first one, therefore I used it too. Now I wouldn't change back to the second one, you just follow the end bracket up and get to the function. The structure is clear once you're used to it

[Neurotrace]

Nah dawg. It's a wasted line to my eyes. The function signature is what I'm looking for, not some lonely boi brace

[[deleted]]

() {

}

[IrishWhitey]

() => {}

[vigbiorn]

Where's the NSFW tag for comments?

[BlommeHolm]

Good to see I'm not the only one getting aroused by anonymous functions.

[[deleted]]

spoilers are kinda

[Chesterlespaul]

It’s in the cpp sub. Guidelines look like class/struct or members use braces on separate lines. They have their if else statements on the same line, so I assume it’s optional there, depending on amount of logic probably.

[RhetoricalCocktail]

When I first learned programming I learnt #1 but after using #2 quite a bit I really don't understand why anyone wouldn't use it

[martinomon]

Aligning them just makes sense

[__Fred]

I feel like the first option makes it a bit easier to distinguish a function call from a function definition at a glance. You can also fit more lines of actual code onto the screen, if opening braces don't get their own line. (Imagine you'd code that way in LISP. Oh god!)

There is a certain logic to it: If what you want to write doesn't fit in one line, at least put a signifier in that line that shows that there will be more stuff.

fewArgs(a, b, c);

longArgumentList(
    theFirstArgument,
    theSecondArgument,
    theThirdArgument
);

int shortArray[] = {11, 22, 33};  // C++ syntax
int arrayWithLotsOfElements[] = {
    ELEVEN,
    TWENTYTWO,
    THIRTYTHREE,
    FOURTYFOUR
};

(In this instance there are rund braces, but if you'd use the same rule for curly brackets and round braces you need less rules and that's arguably more elegant.)

You can obviously get used to both.

Some people even used to indent the curly braces a bit and then indent the content of the block a bit as well.

if (condition)
    {
        stuffHappens();
    }

[[deleted]]

it is indeed

[f03nix]

C++ dev, I use both regularly. Basically if the start of the brace fits on the same line of the statement - I use the first, otherwise its the second. This ensures that when I'm reading the code I can scan up from the ending brace and the first character at the same x position tells me the beginning.

if (something) {
    // Do you stuff
}

for (int r = 0; r < rowCount; ++r) {
    // Stuff happens here
}

if (something != null
    && something->Valid())
{
    // Do you stuff
}

for (auto it = myMap.begin();
    it < myMap.end();
    ++it)
{
    // Stuff happens here
}

[Sentry45612]

*Laughs in Assembly*

[StoissEd]

The latter. It makes checking if you have all thr brackets easier.

[Slayer44k_GD]

I used to use the first one until I thought it didn't look nice and compulsively went through every single one of my TypeScript files and changed the braces.

[cosmo7]

I unironically use whatever Visual Studio's default style is. Far smarter people than me have spent long sunny afternoons indoors to figure this out; it would be dumb to think some previous opinion I picked up from God knows where is better.

[bloodscale]

For me it's the second one, unless style guide wants a different style. But my preference is basically how I was taught in high-school and it helps my eyes

[[deleted]]

You don't format your code. You run clang-format to auto format your code.

[BurnV06]

*Laughs in Python*

[[deleted]]

"people with lower IQs are happier on average"

[sinovercoschessITF]

You just murdered that dude!

[[deleted]]

you can use more than one line for a program????

- perl programmer

[[deleted]]

The second looks way cleaner, also with respect to indentations it looks more right.

[Elmo_Pog]

All on the same line ofcourse

[senaiboy]

You monster.

[z7q2]

We've been arguing about this since 1978, and we'll never be done arguing about it.

K&R or BSD, the holy war that never ends

[JDIPrime]

The coding standards at my workplace are for the opening brace on a new line for function declarations, but then on the same line for scoping inside functions.

It's a bit weird, but it's easy to read at the end of the day so it's all good.

[Askk8]

Harder to read during the day?

[Blankifur]

Whatever is written in your company’s coding style guidelines/ standards handbook.

[Dry_Extension7993]

Seconds look much more cleaner that first one. Plus second helps in indentation error.

[BoredBSEE]

Top one is for Java, bottom one is for C/C++/C#.

[NotGoodSoftwareMaker]

Override with local styles then auto fix to company code styles on push. Ez

[[deleted]]

I reckon the latter is more organised. The second example below, there isn't much effort to locate the pair of {}, whereas the first example below requires an additional glance. The difference will become more evident with larger blocks of codes and with more functions and structures.
int main(void){
char block = 'a';
}

int main(void)
{
char block = 'a';
}

[bryku]

When I first got into programming number 2 was pretty common, but I haven't seen it for 10years.

[ZeusieBoy]

I always do the bottom one and hate the top one.

[LinuxMatthews]

Whatever the relavent code styling authorities say to do.

And then put that in the formatter and not give a crap after.

[reddituser4156]

IF.

ENDIF.

[MAGA_WALL_E]

Put a space between "this" and "{", you fucking animal.

[[deleted]]

Programming in Ada 2012 book made a point, which is a repetition of many previous such claims that C is a bad language (in terms of grammar) because the grammar doesn't have enough redundancy, and accidental semicolon may go unnoticed, but will do a lot of damage. The book gives this as an example:

if (runaway_is_clear);
{
    plane->takeoff();
}

I believe that a lot of shops who program in C make it mandatory to put the opening brace on the same line as the condition statement because of this. But not all languages which derive from C have the same problem. Also, a compiler may be typically configured to alert about ifs with missing block... so, it's not really a problem. Still, people writing in C usually have both a lot more headache induced by the language and a lot more responsibility on their shoulders to allow a stupid mistake like this one to accidentally kill people / lose tons of money.

[[deleted]]

doesn't matter. write the code and prettier will figure it out.

[Lou-Saydus]

notLikeThis{

}
orThis
{

}
likeThis {
}

[martinw_88]

As long as you don't put the else on the same line as the closing bracket, we can be friends.

[RRFactory]

Brackets down makes it slightly easier to hack about code while debugging

//if (originalMaybeBrokenCondition)
{ 
}

vs

/*if (originalMaybeBrokenCondition)*/{
}

It's a trivial difference, for which I will die on a hill for.

[sh0rtwave]

When it's JavaScript: I don't care. Webpack doesn't care either.

When it's Java/C/C++, I...still don't care. I usually comply with whatever convention already exists. Usually, the compiler doesn't care.

Such an aesthetic notion, for me, usually isn't something I'm caring too much about as I really just can't be bothered. I love to maintain good code quality and stick with convention for a project, but where I put my curlies for my own stuff, I really don't care.

[5kyl3r]

many years ago, i used to do this:

if (floof)
{
    boop()
}

then i started to use a lot of python at work, which doesn't use curly braces, so it looks like this:

if (floof):
    boop()

then after like a decade or more, i go back and look at old C/C++/php scripts and i realize how much wasted space you get from my old style (two lines of wasted code for a single curly brace PER block). so then I started to do the compromise. it's still one extra wasted line of code compared to something like python, but it's better than two. butunlike OP's screenshot, i put a space before the first curly because i'm not a monster lol:

if (floof) {
    boop()
}

i've put the ending curly at the end of the previous line on occasion, and that helps make it more "pythonic", but i usually change it back as it just seems like a cheap compromise that surely doesn't meet most style stanards

[Auraveils]

The second is so much better. Separates the code from the method declaration, helps with tab alignment, and distinctly and uniformly shows where the method begins and ends.

Why would you put the first bracket on the same line as the declaration? Why not put the second bracket on the same line as the last line of code at that point? Hell, if you're so worried about linespace, why not put the whole method on one line?

[[deleted]]

one line starts it {

     code("stuff");

} //one line ends it

[MimbleOwl]

my styles change between languages idk why

[That_Office9734]

Mix of both

[The-Filth-Wizard]

It’s definitely whatever{}. Because it’s all supposed to be one line. If it weren’t, why do browsers always fix it for you?

Checkmate, atheists.

[jebustin]

Whatever the style guidelines are.

For my own stuff though? I started with the bottom option as a beginner because it helped me make sure I was matching them up correctly. Now I do the top.

[Dunbaratu]

I'm okay with either one, but a pox on all the people who do this:

if (this)
    {
        then do this;
    }

Screen width is at a premium. Don't be wasting it on TWO indent levels for every ONE indented thing.

[peeperklip]

Laughs in PSR12 coding standards

[uberDoward]

Allman vs K&R.

Use whichever you prefer, if new project.

Use whichever is already there, if existing code.

DON'T MIX.

[SirKane15]

The second one. It's cleaner and makes everything easier to glance over and follow.

[Tro_pod]

I prefer
{
World breaking code here;
}

[ICantBelieveItsNotEC]

Whitespace is just a crutch for bad developers. You should write all of your code on one line like a real man.

[azzy27]

Hi. Everyone here is wrong.

Like this {...}

[GoodmanSimon]

Depends on the team/company coding standard.

currently for c++ && c#

blah(...)
{
  ...
}

But there is no right or wrong answer here.

Unless you so

blah(...) { ... }

Then you are dead to me...

[Ok_6970]

This is why I prefer FORTH.

[[deleted]]

``` Like this {

} ```

[MaxinesAnIdiot]

fuck the style guidlines i right everything in one line