Which one are you?

Which one are you?

correct answer is it doesn't fucking matter.

Whichever one my IDE makes me use :^)

left if you actually care about making your code readable

whatever the code standard for the project requires

>look at me ima pleb

also /thread

prefer right but I'll use whatever is consistent with the code base I'm working with

Left is like having. a period in the middle of a sentence. It's so hard to read.

Depends on my mood

this, but keep it consistent

left for signatures, right for control sequences

I prefer left but will use right depending on the language or code base.

In some languages left can be ambiguous and lead to unexpected behaviour. I think right is acceptable in any brackety language.

or, stop being an autist and use python.

if youre_not_shitty:
return best_code_ever

left

Python is for faggots and Guido is an idiot.

I add the } right after the */ so I'm 3rd way

>only programmers will understand this
>basic conditional control statement that can be found in any pajeet's intro to programming book
Next you're going to say printing "Hello World" is (((""""hacking"""")))

right
left takes up too much white space

For myself? Right.

However if the code standard is different for the project I'm doing, it's a given that it needs to conform to what the style guidelines is for the project.

Left for classes, struts and functions

Right for short statements (around 5 lines). Using right for some massive block of code spanning several screens is retarded.

Your text editor should handle the brackets for you anyways

assert bros_argument == nice

doesn't matter if kept consistent

i prefer allman style though

>left for sjws
>right for uncucked people

If (condition) { Statements /* ... */ }

Keep it inline

This. Used to use left, but then I started taking testosterone and drinking beer and beating up gays, and now I use right.

I was taught to use the right, but I don't really mind either way.

Left for symmetry

Left. Easier to see what's happening where.

Right, because I'm not an asshole.

neither. I tab in from the left one or it auto tabs for me. plebs.

based

Right because I was taught by those who were taught by those who were taught by Richie.

Left is definitely cleaner but I don't like it for some reason.

Left takes up more space but looks cleaner.

>be right
>boss makes me install some config on my ide that configures to left when I ctrl + f
>sonarqube also complains if I do right
welp

>only programmers will understand this
>same as CSS syntax

Cool, I guess that makes me a programmer now. Can I have a job please?

Yeah the mop is over there in the closet. Get to work.

left

I use the left, at least for me it makes my shit way easier to read

Right. It's the way it's meant to be written.

left and right if the ide places it because i am to lazy to change trivial shit like that

>Which one are you?

Right.

Left looks nicer but when you're maintaining code and scrolling through thousands of lines formatted that way you will wish it weren't.

Used to be left, but then switched to right. I think it had something to do with a class I took.

if(Conditions){Statements /* ... */}

This, only use right side if you're a braindead pajeet working for 2 packets of crisps an hour

//
// Something something something
//
if (Condition)
{
// Do Statement by X and Y
Statements
}

Fuck you I'm neither I use a single line for my code.

Right

sick meme i'm gonna go post it on facebook

the former, without a space after if

spot the C# nigger

Right is better, left is using more lines = takes more space = works slower.

I'm no programmer, but I can infer that it's related to code indentation

Stop making programming seem so unreachable ffs

Not really to do with indentation, it's to do with code blocks, which start & end with curly braces.

Some people have start and end braces on seperate lines, which makes it easier to identify blocks of code when scanning through.

And then some brain damaged people have the start brace on the same line as the statement before it, with the end brace on a seperate line. No idea how this took off because it's just plain retarded, "muh one line saved" isn't really worth it when you have a 5000 line source file which looks like shit

Really not an issue with the statement's indenting already serving as a start point.

this

{statement} if (condition)

actually i use Meme++

Its crazy how this threads always get this amount of attention. Its fucking simple, Right one for everything except functions ... Only kernel devs will understand.

USE LEFT IF U DONT WANNA GET LAUGHED AT AND FIRED

THIS

>Whichever one my IDE makes me use
CHANGE IT TO PROPER INDENTATION IN THE SETTINGS

RETARDS

Whatever your team is using. Consistency is what's important. This type of discussion are pointless like spaces vs tabs or Vi vs Emacs. In the real world, it doesn't matter. Only kids who want to define themselves and feel superior care about this bullshit.

THIS!

>spaces vs tabs
BUT USING SPACES WASTES MORE TIME!!

meaningless time. the only time you should care about is the time you take to come up with a solution to the problem.

It's about "which one are you" which means preference. So which do you like to use?

I personally would put the squiggle on a new line, just to make sure I don't miss it.

function() {
statement;
statement;
statement;
statement; }

ew.

Golang forces me to use the right one and I hate it because of it.
But I use it anyway.

if (condition)
{ statements
/*
....
*/
}

if ()
{ statement; statement;
statement; statement;
statement; statement;
statement; statement;
}

Neither. The space ) { looks ugly af.

>return

even python is too hard for you, it seems

whatever the project spec states > whatever the language spec states > whatever I prefer (right side)

>squiggle
Gr8 b8 m8, I r8 it 8/8

New to prog but left looks like the right answer.

Left

I'm calling the police.

Every time I see the right style I want to vomit.

The reasoning I have heard is in the 80's, source code often needed to be printed out on paper, so by leaving out whitespace you save a lot of pages. I don't really know if this is true or not.

It doesn't matter as long as it's consistent
OR
Whatever is specified by the project requirements, company policy, your boss, etc.

void func()
{
if (condition) {
statements
}
}

This is the only wrong answer

Left is borderline retarded you dumb FCK. The bracket is just confusing on that spot. If you really want some white space do right AND PRESS THE FUCKING ENTER BUTTON MONGOLOID.

it takes more time to compile left

left always

I use left. If you want me to use your shitty style provide a clang-format config

Also you can configure your ide/vim/whatever idk anymore to use spaces instead of tabs, jesus people!

(a > b) > ? (c > d) ? e : f : g

i nearly puked when I found this kind of shit in a checkin from some intern

> not even python

Right

But if there's an else, it should get its own line

Its the right-wing plebs

if(condition) {
Statements
*/
...
*/}

lmao fucking idiot

void
func(
void
)
{if(
condition
){statements}}

void
func
(void)
{if
(condition)
{statements}}

Rightislikeputtingallthewordsclosetogetherfornofuckingreasonandactinglikereadabilityisjustasgood.

To be honest I'm genuinely wondering why we still have purely text-based editors in fucking 2016, and why we're still arguing about this kind of thing no compiler cares about.

Neither. I prefer
If Condition
{
Statments
/*
....
*/
}

>purely text-based editors

>his editor doesn't support embedded vector graphics and 3D models

I use left out of habit, I've been doing that way since highschool. Honestly it might take a but if extra effort to make everything look clean, but it really improves the readability of your code which is quite important.

The correct answer is right, prove me wrong.

There.