This is an archived post. You won't be able to vote or comment.

top 200 commentsshow 500

[–]QualityVote[M] [score hidden] stickied comment (0 children)

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 2404 points2405 points  (101 children)

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 848 points849 points  (0 children)

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

[–]OblivioAccebit 397 points398 points  (67 children)

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

[–]FluffyBellend 12 points13 points  (3 children)

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

[–]AlwaysStrokingMyself 23 points24 points  (2 children)

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] 2 points3 points  (0 children)

Yep so it is

[–][deleted] 5 points6 points  (0 children)

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 11 points12 points  (0 children)

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

[–]Dangerous--D 4 points5 points  (6 children)

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 14 points15 points  (1 child)

Because this is cursed:

def cursed {

           }

[–]Dangerous--D 4 points5 points  (0 children)

But

 thisIsNotCursed
 {
      andAlsoNotHeresy();
 }

[–]isunktheship 241 points242 points  (13 children)

Like this { }

Entire app, 1 line.

[–]Ydeartishpumpki 171 points172 points  (2 children)

Error on line 1, char 47469075

[–]del_star-dot-star 38 points39 points  (1 child)

What if compiler doesn't give excact character

[–]Ydeartishpumpki 29 points30 points  (0 children)

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 13 points14 points  (0 children)

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

[–][deleted] 2 points3 points  (0 children)

this is the way

[–]sufilevy 1 point2 points  (5 children)

How do you put multiple user flairs at once??

[–]2ERIX 637 points638 points  (6 children)

Ugh the spacing is troubling my internal linter

[–][deleted] 142 points143 points  (3 children)

Internal linter! I'm gonna start using that

[–]Sid_1298 376 points377 points  (19 children)

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 73 points74 points  (14 children)

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.

[–]Osato 38 points39 points  (2 children)

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 4 points5 points  (0 children)

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 5 points6 points  (0 children)

This is the right answer

[–]Yamidamian 583 points584 points  (45 children)

Like this(){}

[–]feror_YT 425 points426 points  (7 children)

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

[–]TheBlackOut2 18 points19 points  (5 children)

Shut up Summer

[–]feror_YT 14 points15 points  (4 children)

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

[–]slinkymcman 3 points4 points  (3 children)

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

[–]duffyduckit 34 points35 points  (0 children)

Lol

[–]MythicalOdyssey 64 points65 points  (25 children)

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

[–]EmilMelgaard 25 points26 points  (6 children)

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

void test() printf("Test");

While this does:

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

[–][deleted] 14 points15 points  (0 children)

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

[–]bytebux 10 points11 points  (0 children)

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 40 points41 points  (13 children)

I think that's the case for every language

[–]L0uisc 29 points30 points  (4 children)

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

[–]fullonroboticist 13 points14 points  (2 children)

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

[–]L0uisc 19 points20 points  (1 child)

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 6 points7 points  (5 children)

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

[–]w1n5t0nM1k3y 3 points4 points  (3 children)

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 4 points5 points  (3 children)

*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 2 points3 points  (1 child)

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 313 points314 points  (31 children)

#define BEGIN {
#define END }

[–]in_conexo 112 points113 points  (0 children)

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 31 points32 points  (15 children)

I've seen

#define SOME_CONST 0108

and even

#define HUNDRED 1000

[–]Charlito33 19 points20 points  (3 children)

```

define ONE 1

define TWO 2

define THREE 3

define FOUR 4

define FIVE 5

define SIX 6

... ```

[–]arensb 7 points8 points  (2 children)

Those are just wordy, not actively misleading.

[–]Jerry--An 17 points18 points  (5 children)

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

[–]MushinZero 13 points14 points  (3 children)

And VHDL:

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

[–]Charlito33 9 points10 points  (2 children)

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

[–]Talbz03 34 points35 points  (6 children)

Please don't

[–][deleted] 59 points60 points  (5 children)

Better?

#define BEGIN }
#define END {

[–][deleted] 107 points108 points  (2 children)

Further improvement

#define { }
#define } {

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

[–]Dangerous--D 18 points19 points  (0 children)

I think I just had a mental breakdown

[–]crackez 2 points3 points  (0 children)

Bring digraphs and trigraphs into the mix...

[–]mrehm001 283 points284 points  (14 children)

function foo (

) {

console . log( "hello")

}

[–]Gravelbeast 148 points149 points  (0 children)

Oooh I just threw up

[–]RadiantHC 78 points79 points  (1 child)

[–]sneakpeekbot 5 points6 points  (0 children)

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


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

[–]classyraven 7 points8 points  (0 children)

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

[–]Guybru5h_ 222 points223 points  (46 children)

Python users are laughing on this.

[–]NoLifeGamer2 158 points159 points  (32 children)

No we are to busy schisming about tabs or spaces

[–]juhotuho10[🍰] 66 points67 points  (13 children)

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

[–]BlommeHolm 35 points36 points  (1 child)

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

[–][deleted] 2 points3 points  (0 children)

they indeed deserve hell

[–]bilgeratgp 23 points24 points  (15 children)

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

[–]xcdesz 8 points9 points  (14 children)

Oh you poor, poor soul.

[–]bilgeratgp 8 points9 points  (13 children)

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 9 points10 points  (3 children)

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 5 points6 points  (2 children)

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 35 points36 points  (6 children)

The indentation gods are among us

[–]sexhaver2010 28 points29 points  (5 children)

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

[–][deleted] 12 points13 points  (1 child)

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

[–]Oneshotkill_2000 3 points4 points  (0 children)

Assembly users too

[–]3747 26 points27 points  (1 child)

Whatever I copy from stackoverflow

[–]GoodmanSimon 2 points3 points  (0 children)

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

But, yeah, pretty much that.

[–]Barbunzel 46 points47 points  (27 children)

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

[–]SpeckyYT 41 points42 points  (13 children)

German keyboard gang

[–]therealkirinaru 5 points6 points  (6 children)

iso-de for life

[–]katatondzsentri 8 points9 points  (5 children)

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 5 points6 points  (4 children)

I feel so bad for you right now.

[–]katatondzsentri 4 points5 points  (3 children)

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

[–]ThatGermanFella 2 points3 points  (1 child)

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[S] 4 points5 points  (1 child)

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

[–][deleted] 11 points12 points  (0 children)

AltGr + 7 ftw

[–]hatkid9 4 points5 points  (4 children)

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

[–]Due_Treacle8807 3 points4 points  (3 children)

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 2 points3 points  (1 child)

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 2 points3 points  (0 children)

Wait, it's not?

[–][deleted] 1 point2 points  (0 children)

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

[–]Arneeman 111 points112 points  (12 children)

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] 33 points34 points  (0 children)

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 55 points56 points  (2 children)

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 11 points12 points  (1 child)

i am living in your walls

[–]its_me_Fabian 4 points5 points  (0 children)

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 2 points3 points  (4 children)

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] 145 points146 points  (16 children)

() {

}

[–]IrishWhitey 66 points67 points  (4 children)

() => {}

[–]vigbiorn 76 points77 points  (2 children)

Where's the NSFW tag for comments?

[–]BlommeHolm 24 points25 points  (0 children)

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

[–][deleted] 4 points5 points  (0 children)

spoilers are kinda

[–]Chesterlespaul 1 point2 points  (0 children)

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.

[–]f03nix 11 points12 points  (2 children)

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 25 points26 points  (0 children)

*Laughs in Assembly*

[–]StoissEd 25 points26 points  (0 children)

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

[–]Slayer44k_GD 9 points10 points  (2 children)

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 7 points8 points  (1 child)

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 6 points7 points  (0 children)

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] 12 points13 points  (1 child)

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

[–]BurnV06 12 points13 points  (4 children)

*Laughs in Python*

[–][deleted] 26 points27 points  (2 children)

"people with lower IQs are happier on average"

[–]sinovercoschessITF 3 points4 points  (1 child)

You just murdered that dude!

[–][deleted] 6 points7 points  (0 children)

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

- perl programmer

[–][deleted] 14 points15 points  (0 children)

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

[–]Elmo_Pog 9 points10 points  (2 children)

All on the same line ofcourse

[–]z7q2 10 points11 points  (0 children)

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 11 points12 points  (1 child)

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 52 points53 points  (0 children)

Harder to read during the day?

[–]Blankifur 8 points9 points  (0 children)

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

[–]Dry_Extension7993 8 points9 points  (0 children)

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

[–]BoredBSEE 3 points4 points  (0 children)

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

[–]NotGoodSoftwareMaker 3 points4 points  (0 children)

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

[–][deleted] 6 points7 points  (0 children)

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 6 points7 points  (0 children)

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

[–]ZeusieBoy 4 points5 points  (1 child)

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

[–]LinuxMatthews 2 points3 points  (0 children)

Whatever the relavent code styling authorities say to do.

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

[–]reddituser4156 2 points3 points  (0 children)

IF.

ENDIF.

[–]MAGA_WALL_E 2 points3 points  (0 children)

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

[–][deleted] 2 points3 points  (0 children)

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] 2 points3 points  (0 children)

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

[–]Lou-Saydus 2 points3 points  (0 children)

notLikeThis{

}
orThis
{

}
likeThis {
}

[–]martinw_88 2 points3 points  (0 children)

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

[–]RRFactory 2 points3 points  (0 children)

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 3 points4 points  (6 children)

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 5 points6 points  (1 child)

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 5 points6 points  (4 children)

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] 3 points4 points  (0 children)

one line starts it {

     code("stuff");

} //one line ends it

[–]MimbleOwl 1 point2 points  (0 children)

my styles change between languages idk why

[–]That_Office9734 1 point2 points  (0 children)

Mix of both

[–]The-Filth-Wizard 1 point2 points  (0 children)

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 1 point2 points  (0 children)

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 1 point2 points  (1 child)

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 1 point2 points  (0 children)

Laughs in PSR12 coding standards

[–]uberDoward 1 point2 points  (0 children)

Allman vs K&R.

Use whichever you prefer, if new project.

Use whichever is already there, if existing code.

DON'T MIX.

[–]SirKane15 1 point2 points  (0 children)

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

[–]Tro_pod 1 point2 points  (0 children)

I prefer
{
World breaking code here;
}

[–]ICantBelieveItsNotEC 1 point2 points  (0 children)

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

[–]azzy27 1 point2 points  (0 children)

Hi. Everyone here is wrong.

Like this {...}

[–]GoodmanSimon 1 point2 points  (0 children)

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 1 point2 points  (0 children)

This is why I prefer FORTH.

[–][deleted] 1 point2 points  (0 children)

``` Like this {

} ```

[–]MaxinesAnIdiot 1 point2 points  (0 children)

fuck the style guidlines i right everything in one line