[...], it's hard to write code to the GNU coding standards, which are probably the most illegible coding guidelines for C. It's so obvious it was written by a lisp programmer.
-- Marc Espie (*BSD alphafag)
Name:
Anonymous2007-09-17 14:14 ID:ahVo4Gs+
BSDfags should gtfo, GNU style is superior and most readable. They need to get a decent text editor (or the very best, GNU Emacs) and stop coding in vi/ed/whatever
Name:
Anonymous2007-09-17 14:24 ID:WTyss6Vk
>>2 GNU style is superior and most readable the very best, GNU Emacs
Hahaha, GNU/hippy faggot
>>3 OKAY YOU FUQIN ANGERED AN EXPERT EMACS USER
GODFUCKIGNDAMN
FIRST OF ALL, YOU DONT FUQIN KNOW WHAT A MAN PAGE IS
SECONDLY, THIS IS /prog/ DO NOT DEMAND USEFUL ANSWERS THE WAY YOU WANT THEM TO BE
THIRDLY PROGRAMMING IS ALL ABOUT PHILOSOPHY AND ``ABSTRACT BULLSHITE'' THAT YOU WILL NEVER COMPREHEND
AND FUQIN LASTLY, FUCK OFF WITH YOUR BULLSHYT
EVERYTHING HAS ALREADY BEEN ANSWERED IN http://www.gnu.org/prep/standards/standards.html
Name:
Anonymous2007-09-17 14:31 ID:4dSkL7OK
Warning: 320 KB.
Name:
Anonymous2007-09-17 14:36 ID:LPnu0D3c
To support pre-standard C, instead of writing function definitions in standard prototype form,
int
foo (int x, int y)
...
write the definition in pre-standard style like this,
Obvious reason Also I drive to work quickly but still function well I applied BBCode to Python in Python to post a link to a convicing draft on why strong typing is important and?