My code was doing the exact oposite of what I wanted it to do and it took me about 2 hours to find out that strcmp() returns 0 when the strings match, problem solved, fml.

I was shocked when one of my university teachers said there was no difference between strcmp(input, exit); and strcmp(input, "exit");

strcmp() is the most confusing function of all time. It returns zero when everything matches.

LOL that's why I love C!

The function pointer cast for strcmp because qsort expects a compare function with two const void * pointers instead of two const char * pointers, that's just beautiful.

Not to mention the hack to abuse strcmp on a struct - which just works because the first struct member is a string and the rest just gets swapped with memcpy as opaque data.

I guess that wouldn't pass a code review at work. :-)

People here expect me to use strncmp(str,"ABC",strlen("ABC")) because they think strcmp(str,"ABC") is going to crash. Because they've had experiences of using strcmp and getting crashed.

All they did was, pass inside strcmp, strings that did not carry terminating null character but won't accept if i told so.

They used strcmp (PHP) on the main server as only form of authentication...

The strcmp(3) manual page takes me closer to god: "strcmp() function compares the two strings s1 and s2. It returns an integer less than, equal to, or greater than zero if s1 is found, respectively, to be less than, to match, or be greater than s2."