Legit question, guys...

>>52548139
B

A

>>52548139
A for java, B for C#

>>52548139
A

File: 1453209861114.jpg (85KB, 500x628px) Image search: [Google]

85KB, 500x628px

>>52548164

A is more professional. B is a bad habit that new programmers pick up.

>>52548139
B

Neither.

I'm not an 18 year old who just finished programming 101 so I don't need to use the print function in any language.

>>52548180
How does it make a difference?

A by a long stretch

Is it bad that I do A for for, while, if and B for functions? Only in C++. In Java it's always B.

>>52548139
I prefer A myself, but I've seen a lot of examples in B format.

I think it's the influence of Dennis Ritchie or some sort...

>>52548139
I personally prefer A, but both are pretty readable.

>>52548193
It doesn't. It's just bad form. Most people use A, so when I'm reading code for someone that uses B it just makes it more tedious.

>>52548139
Ooh I hate B so much. Fuck B, it shouldn't even be syntactically correct.

File: 1451184312060.jpg (160KB, 600x1467px) Image search: [Google]

160KB, 600x1467px

>>52548139
A is the only answer, it always has been and always will be the objectively correct way to do it. B is literal cancer created by degenerate reddit scum.

int main()
  {
    printf("OP is a faggot");
  }

>>52548204
>Is it bad
yes because of the lack of consistency.

B

>>52548215
Fair enough, I thought you were going to say something like
>muh space

>>52548174
nice choice

>>52548164
>>52548184
>>52548204
>>52548225
>>52548228
>>52548264
Seriously, just stop trying and fuck off.

>>52548264
Sorry cocked that up

B is correct in this case, however neither are correct. It should be:

int main(void)
{
    puts("Hello, world!");
    return 0;
}

And of course for anything other than functions, the { should go on the same line where appropriate, like in A.

A

>>52548139
A for college.
B for everything else.

>>52548139
A

>>52548287
ayy
>>52548204

>symbols denoting the same scope having different indentation

A just hurts.

B only for function/class/namespace blocks

for everything else, A

>>52548139

A

>>52548139
A, Only n00bs use B

>>52548139
B master race reporting in. A looks like it was placed randomly

>>52548139
B

File: 146383268123.jpg (4KB, 191x200px) Image search: [Google]

4KB, 191x200px

>>52548225
>calls OP a faggot
>using B
>with a tab, no less

when I format my code in visual studio it chooses B. I trust visual studio.

>>52548139
For C++ it's definitely B.
A is for javaScript.

>>52548139
A

>>52548180
>A is more professional
Depends what language you're using. When I write C/C++ i use B. When I use languages that make heavy use of closures/lambdas etc... I'm more prone to A.

I like B better though, delineates block level scoping better in my opinion.

A is cancer

File: oldpasta.jpg (20KB, 183x275px) Image search: [Google]

20KB, 183x275px

>>52548139
So many amateurs these days.

When mootles was in charge, every even numbered reply would point out no int is being returned, every other would be greentexting the lack of newline

B. A is a holdover from days when displays did not have resolution for enough rows so saving vertical space at the cost of readability was justified.

>My preference is the professional option
>There are people ITT who aren't PRO like me.

>>52548139
B

int main()printf("Hello, world!");

People still use curly braces?
Wew lad. It's 3740 for Christ's sake.

>>52548371
>calling others amateurs
>thinks you need to return from main

>>52548139
YOU ARE NOT RETURNING AN INT YOU FUCK.

>>52548384
mah nigga

>>52548174
I concur

>>52548225
GNU style
Not even once.

File: 1438037049785.png (142KB, 850x800px) Image search: [Google]

142KB, 850x800px

Anyone who says anything other than A are faggots who care and boast about code lines.

>>52548396
This

>>52548139
B. A makes shit unreadable and messy as fuck.

>>52548396
Spotted the retard who doesn't know C.

>>52548409
I get my wage from amount of code lines and I'm not even indian.

>>52548371
>A newline
>Necessary for a single print that was only ever intended to be an example for OP's question
Well autism must be at an all time low then.

>>52548415
Spotted the retard who doesn't use pure ANSI C for everything with `clang -std=c89 -Weverything -Werror -pedantic-error`

>>52548384

<stdin>: In function ‘main’:
<stdin>:1:11: error: expected declaration specifiers before ‘printf’
<stdin>:1:11: error: expected ‘{’ at end of input

>>52548452
C11 is the only version that matters.

>>52548452

clang -Wew lad

>>52548466
> using traditional compilers

>>52548435

Did you mean all time high? Because saying my autism being low makes me think you want to suck me off

>There are people ITT agonizing over a basic hello world program that was merely intended to give examples of bracket placement

>>52548164
>>52548184
>>52548228
>>52548264
>>52548287
>>52548304
>>52548327
>>52548334
>>52548338
>>52548375
>>52548383
>>52548411
cancer autists confirmed

>>52548452
How barbaric. C11 is the standard, that's what I compile with. Weverything, Werror and pedantic-errors (for future proofing) are just common sense.

>>52548191
how is this even related to the print functions you fucking retard?
fuck I took the bait didn't I? fuck me

>>52548191
No, look at the brackets.

>>52548496
No lad.
>So many amateurs these days.
But you were twisting your nipples over nothing so if there are a lot of 'amateurs' today who don't give a shit about an hello world program that was only meant to be an example then autism must be at an all time low.

they both look the exact same except for one { key

>>52548571
That makes all the difference, m80.

>>52548539

So you ARE wanting to suck me off - sorry pal I'm married

>>52548591
well B looks more clean imo

File: a.png (9KB, 542x207px) Image search: [Google]

9KB, 542x207px

>>52548139
Hello, I'd just like to interject for a moment...

>>52548618

What does it feel when those jelly eggs go up your ass?

>>52548513
You do realize that -Weverything -Werror would make most things impossible to compile right? Since it warns about things like the fact that a struct has padding in it.

I wouldn't use C11 though and would at the worst only use C99 if it would be impractical to use ANSI C, since a lot of operating systems in use currently don't come with gcc which supports C11, which is enough reason to say C11 is unsupported newfangled garbage.

>>52548507
Actually having the { on its own line for functions in C is proper K&R style, which is the standard which most things use. Having all {s on their own line is nasty though. That should only really be done for C# since that is their official standard code style.

>>52548618
Wow what an autist.

File: whitesmiths.png (21KB, 433x480px) Image search: [Google]

21KB, 433x480px

I like whitesmith's the best, pic related.. But in the future I will try to use B because of shitty standardization rules. God they are both unreadable

>>52548164
Fucking idiot

>>52548626
Objectively the best style.

>>52548139
A because B sometimes doesn't work.

#include <stdio.h>
#include <stdlib.h>

const char* HELLO_STR = "Hello, world!\n";

int main(int argc, char** argv) {
    printf(HELLO_STR);
    return EXIT_SUCCESS;
}

fly you fools

Based Go enforces A

>>52548665
Fucking idiot

>>52548642

Pretty warm to the touch, a little rough against the prostrate because of the texture.

Your curiosity about anal exploration does not go unnoticed, anon

>>52548683
>Letting a compiler tell you how to lay out your brackets
What a cuck!

File: 8a3.gif (2MB, 336x200px) Image search: [Google]

2MB, 336x200px

>>52548626

>>52548689
I'm suing you for copyright infringement

You fucking idiot

U dun goofed nigga

>>52548690

That's fine by me.

I've always been curious about making better use of my prostrate since I accidently gave myself an orgasm.

And I've heard of this thing before.

>>52548694
The government enforces building codes and shit. This is essentially the same idea.

File: 1452665521538.jpg (59KB, 521x521px) Image search: [Google]

59KB, 521x521px

>>52548139
seriously though, why is the method promising to return an int? I don't get it.

>>52548736
Seriously?

File: 1315697101477.png (56KB, 463x646px) Image search: [Google]

56KB, 463x646px

B as used by GNU, Linus and more importantly by Carmack.

I'm fine with either, shit only gets real when the code format randomly changes between the two

>>52548645
I compile other people's programs with whatever their makefile has in it.

My stuff is written in standards compliant C. I don't really even need the C11 features most of the time, so the code compiles just fine even with C99. What I do use from C11 is generally available in the newest versions of GCC and Clang.

And I was just shitposting earlier, anyway. If I target older machines or go for maximum portability, I use C89 like a sane person. Still -Weverything -Werror -pedantic-errors because nonstandard C is not C and not good for portability.

And Allman style is better. It's much more readable, denotes blocks more clearly. No proponent of Egyptian brace in this thread has given any justification.

>>52548678
>putting spaces before the * rather than after
>using an exported pointer in your program which isn't reusable anywhere (rather than writing `static const char *`) rather than a macro in its own header file
>putting something which isn't a macro in allcaps
>not namespacing your HELLO_STR as HELLOWORLD_HELLO_STR
>using printf when you're not formatting a string
>not using K&R { style
>having unused parameters argc and argv instead of the alternative standard main prototype of `int main(void)`

Is there anything inherently wrong with using B?
Why would anyone care in the first place? Sounds like something an autist would do.

The styleguides for 90% of web dev departments say A.

The styleguides for 90% of C++ programming departments say B.

In fact the company I worked at used a lot of WebGL and use style B for all their GLSL code just because it LOOKS like C++ even though a lot of the time it was written inline with JavaScript which was in style A.

>>52548761
>>52548763

these

>>52548139
I prefer B. Makes it easier to see where curlies end and start. Oldfag coders do A, which is perfectly fine.

>>52548770
C++ is a fucking retarded language which is mostly used by retards who want to code games.

>>52548754
yah, I thought you return void you're not returning anything don't you? I only know a little bit of java I'm not that advanced.

>>52548731
>Wanting a coding government
Wow, why don't you just join the NSA?

>>52548736
In C main() returns an int to the OS denoting the exit status of the program. This goes hand in hand with the Unix convention of a program exiting with 0 if successful. And they're called functions in C.

>>52548765
-Weverything isn't and shouldn't be used by anyone. It's some weird feature of clang which enables literally every possible -W flag.

`-Wall -Wextra -pedantic` is what you should be using. You cannot expect any reasonable valid C program to not show any warnings with -Weverything, so that with -Werror would be unusable.

>>52548799
It's for an exit status...

>>52548139
A everywhere

>>52548824
>"""""A"""""" everywhere
A isn't an option.

File: karlore.jpg (17KB, 308x252px) Image search: [Google]

17KB, 308x252px

>>52548807
thank you, never used C before but now i know!

>>52548769
It doesn't matter as long as you stick with one. If you change between the two in the same project, shit gets harder to read and uglier.

I prefer B but I won't complain about A because I'm an adult and I care about consistency more than the specific style. The GNU one is stupid, though. I hope I don't have to contribute to anything written like that.

There's an important semantic aspect that makes A objectively better:

The part defining the function is a tag that's bound to the code in a block. When you have a block without a tag like

{
  print 5;
}

you will use 1 line for the start of the block. With A you will still use 1 line even if you decide to attach extra information to the block.

Also note that the start of the block (return type) and the end of the block (brace) are still perfectly aligned in A

>use A
>use Visual Studio
>puts B style everywhere else

pls

Whatever the project uses. Personally, B.

>>52548859
Well, creating something with consistency is just common sense, it's not exclusive to coding or programming.
Inconsistency is a sign that the person is probably incompetent.

>>52548164
B is how we do it at work. Whilst I always used A, at work everyone has dual 30" 2k's. So saving space is really not an issue. Now I always use B, for C/C++ and C# .NET.

>>52548818
It's easy to pass -Weverything if you know the standard reasonably well and read the warnings/errors it gives. That's why the warnings are there. Having a newline just before EOF is probably unnecessary, but won't hurt me in any way, either.

B, easier to see and more lines of code to show off :3

>>52548920
>>52548769
IMO >>52548892 is a sound argument for A. Also I find it more readable personally

>>52548139
A.

>>52548934
Of course, but -Weverything has a lot more than just helping you write good conforming C. -Weverything warns about things which are 100% perfect valid C. They're more like notices stating the obvious. Do you really need to know that a struct has padding in it? Would it be more correct to add a bunch of pragma packed nonsense or add loads of unused char []s in there just to get rid of some "this struct is padded" warning?

Have you ever even used -Weverything?

>>52548892
You're the first person ever I hear a good argument for A from. I still prefer B for legibility reasons, but that is actually a pretty good reason.

>>52548139
A

>>52548952
Yeah, it's a legitimate argument.
A good rule of thumb would be something like:
1) Individual project = your preference
2) Company/group project = discuss or just follow what format everyone else is using

>>52549007
>>52549071
Yup, I don't really have any problem with either. Used to use B, but switched because I wanted to try out the other option too

def main():
    print("Hello world!")

function main()
    print("Hello world!")
end

>using a language with curly braces

>>52548626
Kek

I usually do this 2bh

void function()
/*
    Prints "Just fuck my shit up family"
*/
{
    printf("Just fuck my shit up family")
}

>>52548139
{
B;
}

>>52548736
>method
Poo in the loo.

It doesn't matter, just use what everyone else does at work.

>>52549213
>using just one language because you don't have a job and can only do hello worlds

>>52549213

main = putStrLn "Hello world!"

>using a language without scientific notation

>>52548139
A, even though my professors keep saying to use B so we don't get "confused". B is if you don't have the mental capacity to keep track of brackets.

>>52548139
I just press CTR+ALT+L and see what the IDE does.
if i'm not satisfied i change the coding style

>>52548139

B is vastly superior.

A is only valid in two circumstances:

1) You're on an old-timey terminal and only have 25 vertical lines (i.e. vertical space is precious).

2) You're writing Javascript which, thanks to the stupid optional semicolon, needs open braces on the same line.

>>52548139
I use B for loops and A for everything else.

>>52548139
a

File: C.png (346B, 243x50px) Image search: [Google]

346B, 243x50px

If you're not doing right ffs
If you don't do this you will never get hired at $big_enterprise (80k starting)

>>52548139

int main()
{
    while (1) {
        puts("1TB or fuck off");
    }
    return 0;
}

xD

I started out with B when I was in highschool but switched to A when I started getting internships.

>>52550370
First one, the fact that it's one line longer shouldn't even be an issue.

>>52550370
The first.

So B.

Using anything else is cancer. Yes even python.

>>52548139
Why not both?

Just don't use the no braces method.

>>52550370
22, 23, 26, 27
fix that indentation please

>>52548139
Fucking attach a poll next time tardboy.
A all the way.

I do B most of the time but I feel compelled to do A when I'm writing Java code.

int 

main(void)
    {
        printf("Hello, world!");
    }

>writing code
>not just asking nerds to do it for you in /dpt/ and stackoverflow

File: 1447117283637.jpg (32KB, 560x560px) Image search: [Google]

32KB, 560x560px

>>52548139
>creating a new line just for a bracket

File: >fixed.png (22KB, 433x480px) Image search: [Google]

22KB, 433x480px

>>52548658
>I can see invisible spaces

B
It's how K&R and the Linux kernel team say to do it. That's good enough for me.

B

>>52548384
This isn't ISO compliant code

>>52548139
B is correct because k&r

They have the same output, and one isnt 'more professional' than the other, you guys really are fucking retarded.

>>52550921
int main(){return(printf("your dumb\r",124,123,5));}

File: 1430446052518.jpg (20KB, 314x305px) Image search: [Google]

20KB, 314x305px

>>52548139
B no exceptions. If you use A you are actually retarded and you should probably consider sleeping in a running a car in a small garage.

File: golfing.jpg (20KB, 400x266px) Image search: [Google]

20KB, 400x266px

>>52550971

main(){puts("ur dumb\r");}

A is for virgins.

>>52548139
How is this legit? The only sensible choice is A

>>52548139
>2016
>not using puts() when appropriate

int main()
{
    puts("Hello, World!");
}

>>52548139
B

>>52548139
I'm an A type of guy.

>>52548139
A if you code less and optimized
B if your code is laggy piece of shit nigger, and i hope 28 cactus will be shoved in your ass

File: 2016-01-21_18:30:05:396637206.png (110KB, 806x1244px) Image search: [Google]

110KB, 806x1244px

Here's the style I use. B style for function declarations, because they cannot be nested, and to make the blocks very clear. I use A style for everything else. A style is especially good for if else statements, they save a lot of lines. No curly braces for one statement blocks, thats just a wasted line. My style is very similar to linux kernel style.

Also a weird thing about my style, I put modifiers like static on the line before the function prototype to be more consistient with function prototypes, I find it more readable.

>>52551736
>A if you code less and optimized
Optimization has nothing to do with how much code you put down. Golfing your code doesn't make any difference, if you're writing any compile language.

>>52548139
A
Eclipse autoformat agrees with me
So does intellij

>>52551767
That's how I do everything, but without the arbitrary line spaces in the code and I also use 8 space tabs.

>>52548375
How is B any more readable than A?

A by far. Dont need my code to be an extra 1000 lines for one damn bracket.

>>52551806
They aren't arbitrary, they're like little blocks. I first wanted to declare and initalize accum, so I declare it, then have all logic to initalize it. After that I put a newline to end that block. Next up, I wanted to iterate and print, so I declare i because I need it for that block, and then I iterate and print.

>>52548426
Wait is that a real thing?

>>52551858
I don't see why you need to visually separate such simple operations. If something is significantly different enough to warrant a new block, I usually put it in its own function.

>>52548626
This is the only acceptable way of writing functions

>>52548139
A

>>52548626
that is fucking pig disgusting

>>52548139
B

>>52548472

> -Wew

lost it

>>52548769
That's because it is something only autists care about

>>52548139
A

I interviewed a guy today and he used style B. We didn't hire him.

>>52548164
/thread

>>52548426
I never want to read your code.

File: cb4f6fe4a4c3db368c4adcb0eb88034b.jpg (3MB, 2121x3000px) Image search: [Google]

3MB, 2121x3000px

int main {
    printf("Hello, world!") ;
}

discuss

>>52551893
visual clarity really, makes it easier for the reader later on.

>>52548426
>literally paying for bloatcode
I'm so glad retarded boomers are still bosses

>>52548761
>B as used by ... Linus

Chapter 3: Placing Braces and Spaces

The other issue that always comes up in C styling is the placement of
braces.  Unlike the indent size, there are few technical reasons to
choose one placement strategy over the other, but the preferred way, as
shown to us by the prophets Kernighan and Ritchie, is to put the opening
brace last on the line, and put the closing brace first, thusly:

    if (x is true) {
        we do y
    }

This applies to all non-function statement blocks (if, switch, for,
while, do).  E.g.:

    switch (action) {
    case KOBJ_ADD:
        return "add";
    case KOBJ_REMOVE:
        return "remove";
    case KOBJ_CHANGE:
        return "change";
    default:
        return NULL;
    }

However, there is one special case, namely functions: they have the
opening brace at the beginning of the next line, thus:

    int function(int x)
    {
        body of function
    }

Heretic people all over the world have claimed that this inconsistency
is ...  well ...  inconsistent, but all right-thinking people know that
(a) K&R are _right_ and (b) K&R are right.  Besides, functions are
special anyway (you can't nest them in C).

When I started, A.
Now I can't imagine ever not using B.

B you faggot

Always used A, no idea or reason why, just have

>>52548139
B for function definitions (and a one-line comment that says

// start main

)

A for blocks of code for control statements and loops etc.

>>52548139
>>52552506

Also, shouldn't proper function definitions be

int main(void)

for the C1X standard?

>>52552029
I dunno man, I follow by the principle that I can figure out any line of code on its own (unless it's a weird API call or some embedded system shit) and that there should be a comment above every method saying what it does.

B

>>52552365
What book is this from?

A

File: allman style.png (132KB, 942x739px) Image search: [Google]

132KB, 942x739px

>>52548139
>used to use A all the time, and swear by it
>decided to try B
>never went back
it's just so much more readable

>>52552641
https://www.kernel.org/doc/Documentation/CodingStyle

>>52548180
How is it more professional and why is it a bad habit?

I just do B because it's easier to proofread when I don't have auto completion on the brackets.

A for everything
B for CS grads

I prefer B but I use A. I used B when I first started because it made sense, but A is easier to type since its one less keystroke per bracket.

>>52548139
{
B;
}

>>52548371
What are default return values?
What are irrelevant details to the question?

>>52552844
>one less keystroke per bracket
space, bracket, enter
vs
enter, bracket, enter

I'm not sure I see it desu

>>52550135
kill yourself

>>52548139
B

>>52551767
This is a what I do

>>52553466
I don't use a space for A

File: nigel seriously hopes you guys don't do this.jpg (779KB, 1536x2307px) Image search: [Google]

779KB, 1536x2307px

>>52553728
You fucking what?

>>52548802
What's wrong with the NSA?

B

>>52552015
no one else does space before semicolon?

So long as you've got a decent IDE, A.
It can be pretty hard to keep track of things in shit like arduinio though, especially with the clusterfuck of hacky workarounds that nearly every library seems to be built on, so definitely B for that.

>>52553801

int main(){
...
}

No space before the first squiggly bracket

>>52548226
Going for consistency isn't always the best policy.

This is an old debate.
This is the way I see this issue:
More experienced programmers use A.
Inexperienced programmers use B.

If you don't understand why, then you will side with the inexperienced programmers and choose B.

That is all.

>>52554011
That is the most fucking disgusting thing I've seen all day and I found a dead rat that had partially decomposed drenched in water from a leaking tube behind my fridge this morning

>>52554092
;:( pls no bully

A for internals
B for functions
example:

int main()
{
    if(wat){
        std::cout << "butts";
    }
}

>>52554123
It was a writhing mass of maggots and bits of rotting skin anon

A

File: original.jpg (39KB, 1440x900px) Image search: [Google]

39KB, 1440x900px

>>52548139
>2019 + 4 - 7
>needing silly symbols to define everything

geesh

>>52554229
>2011+5
>needing silly whitespace to define everything

jeesh

>>52548139

local format = "shit"
if format == "shit" then
    print("{ & } looks disgusting")
else
    print("Lua is beatiful")
end

>>52554165
may nigga.
Though I also like to insert a space after 'if' and another before the curly bracket of 'if'.

>>52552699
this desu senpai
curly brackets not being on the same vertical line triggers my autism now

>>52554308
It's not even (entirely) about vertical orientation either, just having a more-or-less blank line delineating scopes horizontally makes the structure of everything pop out so neatly

print('Hello, world!')

The way of the future guys

>>52548139

int
    main
        (into argc, char* argv[])      {
                                                         court << "hello, world!");
                                                         return 0;
                                                        }

>>52554366
way of the meme

>>52551767
The only real answer in this thread

File: 716.jpg (21KB, 388x589px) Image search: [Google]

21KB, 388x589px

>>52548626
nigga....

>>52548139
A for functions, B for methods or loops.

>>52554761
>this