Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon. Entire thread

What stirs your rage, /prog/?

Name: Anonymous 2013-09-14 1:07

Mine are people who do this on C-like languages:
if(numbers==NULL)
{
numbers=temp;
numbers->next=NULL;
}
else
{
temp2=numbers;
while(temp2!=NULL)
{
var=temp2;
temp2=temp2->next;
}
temp2=temp;
var->next=temp2;
temp2->next=NULL;
}


No spaces between operators.
Opening brace on lines by themselve.
Else statement not a continuation of the if-statement it belongs to
Terse variable.
camelCase

Name: Anonymous 2013-09-14 1:11

People who refer to dromedaryCase as CamelCase.

Name: Anonymous 2013-09-14 1:15

Else statement not a continuation of the if-statement it belongs to
Do you mean:
if (predicate){
// something
} else {
// alternate
}


I fucking hate when people do this. It's one of my programming pet-peeves. I scan the block level by line, if you put else after a brace it's harder to see and it just looks retarded. The only time you can put anything after a brace is in:
do {
// something
} while (condition)

Name: Anonymous 2013-09-14 1:19

>>3
I always do the } else { thing, stop being a sissy faggot.

Name: Anonymous 2013-09-14 1:33

One-letter variables, and faggots like >>3.

Name: Anonymous 2013-09-14 1:57

>>3

But you are wrong though. In long programs.

}

else


makes the else harder to distinguish which if-clause it branches from.
On the other hand,
} else { makes a clear distinction and it's not harder to see at all.

Name: Anonymous 2013-09-14 2:23

>>6
It branches from the previous brace, what is so hard to distinguish about that?

Name: Anonymous 2013-09-14 2:24

int
foo
(
char bar,
long baz
)
{
// ...
}

Name: is.gd/MWkdLJ 2013-09-14 2:27

>>1
K&R lover.

Allman Master race!

[spoiler]Although I appreciate GNU style[/code]

Name: Anonymous 2013-09-14 2:29

I tuck mine in.

if (foo) {
bar();
baz();}
else {
hello();
world();}

Name: Anonymous 2013-09-14 2:33

>>10
Terrible!

Name: Anonymous 2013-09-14 3:16

>>10

Might as well write an FOIC compiler for C

Name: Anonymous 2013-09-14 3:30

>>12
cython

Name: Anonymous 2013-09-14 4:17

I hate Lisp. I hate Lispfags. I hate functional programming

Name: Anonymous 2013-09-14 8:03

I hate pretty much any code I don't write.
I also end up hating a lot of the code I write.

Name: Anonymous 2013-09-14 13:51

I don't like FIOC, but I don't like
if ( 1 )

{

penis ( ) ;

}

either. What does /frog/ think of something like
if (1)
penis1();
penis2();.

There's no need for then, and the if scope ends once the period is reached. Also, no indentation is being forced here, you could just write the whole thing in the same line.

Name: Anonymous 2013-09-14 20:50

>>16
looks gay

Name: Anonymous 2013-09-14 21:21

>>14
Kill yourself scum.

Name: Anonymous 2013-09-14 21:46

>>14
yeah, they think they're so 1337 because they know Lisp
I feel sorry for them

Name: Anonymous 2013-09-14 21:50

>>19
Go away.

Name: Anonymous 2013-09-15 0:32

>>17
Suggest something else then.

Name: esp. his link 2013-09-15 0:54

Name: Anonymous 2013-09-15 14:08

>>22
I was trying to avoid curly braces, ``faggot''.

Name: Anonymous 2013-09-15 15:44

Preprocessot shit.

Name: Anonymous 2013-09-15 19:44

People who add redundant comments like this:
#ifdef SOMETHING
...
#endif // #ifdef SOMETHING

Name: Anonymous 2013-09-15 19:50

>>25
If there's nested ifdef's that's useful for knowing which ifdef that endif belongs to.

Name: Anonymous 2013-09-15 20:17

In python I always include an else for every if:
if dicks >= 50:
enoughdicks = 'yup'
else:
pass

Name: Anonymous 2013-09-15 21:06

>>26
If you can't keep track of your #ifdefs, then you're doing it wrong.

Name: Anonymous 2013-09-15 22:11

>>27
why?

Name: Anonymous 2013-09-16 9:10

>>29
So he can feel like an ENTERPRISE PROGRAMMER.

Name: Anonymous 2013-09-16 10:20

People arguing about brace styles stirs my rage. If you can't be bothered to run a beautifier before you begin to read/modify source, fuck you. If you can't be bothered to run a beautifier with a different set of options before you send patches back, fuck you. If you care at all about style but can't be bothered with informing people how to make their code conform to your style (i.e. put ``please run `indent -kr' on all source files before sending patches'' in the doc somewhere), fuck you.

Name: Anonymous 2013-09-16 11:03

>>31
Amen.

Name: sage 2013-09-16 11:07

>>31

Fuck you.

Name: ‮‭ 2013-09-16 11:47

>>33
What, you hate properly indenting your code when submitting a commit? What a Jerk. No wonder I never see your commits, sage.

Name: Anonymous 2013-09-16 12:45

I hate it when people //comment like this.

Comments should be placeable anywhere and capsulable

Name: Anonymous 2013-09-16 15:04

>>31-35
Fuck you.

Name: Anonymous 2013-09-17 13:32

>>36
Fuck you.

Name: Anonymous 2013-09-17 19:35

>>37
Fuck you.

Name: Anonymous 2013-09-17 21:04

No space between code and comment.
int foo;//comment

Name: Anonymous 2013-09-18 12:19

Lazy evaluation. It just doesn't scale...

Newer Posts
Don't change these.
Name: Email:
Entire Thread Thread List