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

autist shit that pisses you off

Name: Anonymous 2016-01-10 19:21

* SLOC instead of LOC
* only one return per function

Name: Anonymous 2016-02-20 13:09

>>40
We who favour a larger rump approve of this restriction.

Name: Anonymous 2016-02-20 20:14

>>41
You like whitespace delimitation and you cannot lie?

Name: Anonymous 2016-02-20 22:26

>>42
That's racist!

Name: Anonymous 2016-02-20 23:57

These are dubs!

Name: Anonymous 2016-02-22 9:28

>>1
/prog/ threads.

Name: Anonymous 2016-02-22 18:01

Embedded vim settings inside of source code file. Instant rage quit. Like following:
https://github.com/tworaz/libhybris-mer/blob/master/libhybris/hybris/include/hybris/dlfcn/dlfcn.h

Name: Anonymous 2016-02-22 18:06

>>46
Sweet, sweet Emax pain.

Name: Anonymous 2016-02-22 18:13

>>46
Emacs untermensch are even more annoying with their "// -*- Mode: C++; c-basic-offset: 8; indent-tabs-mode: nil -*-" at the top of the file:
https://github.com/queezythegreat/arduino-cmake-tests/blob/master/libraries/FastSerial/vprintf.cpp

Name: Anonymous 2016-02-24 13:57

>>46-48
It's doubly annoying for vim since it has had per-directory .exrc / .vimrc support for forever. Emacs doesn't have an equivalent feature that's as widely used. Thus if you see a vim user with mode lines it means they are clueless, or an Emacs refugee.

Name: Anonymous 2016-02-24 14:56

>>26
They do it because they're writing C89 and // comments aren't C89

Name: Anonymous 2016-02-24 15:04

>>26,50
I came for the C89 but stayed because I decided // comments looked ugly (at least for big blocks).

Also, there's no shortage of little languages (mostly inputs for old Unix tools, like ld and variants) that only recognize /* */ comments.

Name: Anonymous 2016-02-26 11:23

People confusing Java with JavaScript. In 2016.
Its like their only expirience with Java was some applet.

Name: Anonymous 2016-02-26 14:58

JEWusalem

Name: Anonymous 2016-02-27 11:56

>>49
they are clueless
he is clueless

Name: Anonymous 2016-03-01 10:09

>>50

But Titor-san, it's no longer year 90. Thats what "new code" means, when you're using something better than Turbo C 2.0/VC6.

Some statists are also shocked and offended by free declarations, you know, those vile things not right after opening brace. Those dirty statements introducing variable scope anywhere surely can trigger the OCD-C habits formed in teens. Such anarchy! How can they allow this?!

Name: Anonymous 2016-03-10 14:46

>>55
If you're using a crap compiler (or a good one, with most optimizations disabled), non-free declarations are useful as they allow the function's stack usage to be appraised at a glance. Granted most compilers will try to keep only live variables around and in registers wherever possible, but a big pile of declarations up top is still a good sign that a function is doing too much.
Newer Posts
Don't change these.
Name: Email:
Entire Thread Thread List
All trademarks and copyrights on this site are owned by their respective parties. All comments and posts are the responsibility of their own posters.
- Tinychan + 2ch Mode + RSS -