Check out do_exit written by linus himself. Looks like redundant blank lines has been sprinkled at random. Same goes for multiline comments, some times there is a blank line preceeding it, some times not. Indent is inconsistent too.
>>12
Define what >>4 said, what's the rule for readability? Of course it has to be unambiguous otherwise it's just subjective fluff. Sloppy I'd say, "what ever you feel is readable for the moment."
>>15
Now point me to a abelson and sussman quality analysis of blank spaces...
Name:
Anonymous2013-01-25 11:53
>>16
No because my le sides still hurt from "E/G/IN /G/IN /G/RO" and "/G/ROSKI".
Name:
Anonymous2013-01-25 11:56
I don't even know what it's suppose to mean, it's like laughing at random garbage. But, you know, kids can have fun with anything so in some way I understand, altough I really don't, what the fuck?
Name:
Anonymous2013-01-25 12:00
I wonder how many professional programmers with deep insights into programming visits this board. I don't count Linus, as he has done a well job displaying all of his incompetence by GPL-ing his source. I'm talking Sussman and Abelson quality! Can I only count myself? That's it?
Name:
Anonymous2013-01-25 12:05
>>19
I don't know if it counts but I masturbate to anime a lot. That makes me a professional programmer, right?
>>20
i masturbate a lot to guys passionately sucking on ass flowers, i suppose it's a lisp thing.
Name:
Anonymous2013-01-25 12:59
I write like this: void *foo (void) {
void *bar = faggot();
if (bar == NULL) {
return NULL;
}
return anus(bar);
}
Not making a new line for opening braces saves lines in the long run, but requiring braces for single statement loops and conditionals has the side effect of introducing an amount of ``pseudo-whitespace.'' I rarely feel the need to add superfluous whitespace as a result.