Funny C Rules (And Low-Level Languages in general)

[frag.machine]

[Baker]

[mankrip]

[Baker]

[jitspoe]

I wonder if it's a rule that /* */ comments are treated as whitespace, or if that behavior could vary from compiler to compiler. Obvious approach is, "Don't do that!"

[Baker]

[Baker]

Shortcircuit operators don't yield the same result as non-shortcircuit operators.

if (2 & 1) // Non-shortcircuiting. Will evaluate to false because 2 AND 1 = 0 (bit operation)

if (2 && 1) // Shortcircuiting. 2 will pass. Then 1 will pass. Will evaluate to true.

[mankrip]

[Baker]

[r00k]

everything is false until it's true.

[mankrip]

[Baker]

[Spike]

one leading underscore is reserved for the libc.
two leading underscores are reserved for the compiler.
I have no idea who four leading underscores is reserved for...

[revelator]

One particularly funny one i seen in C is tag names
#define thistag L# or LL# for 64 bit long long names.
Took me a while to figure out that one and some compilers dont like tags.

[Baker]

I've been thinking of calling conventions lately.

Then I realized something.

WinMain and the message handling function (tends to be named something like MainWndProc or such in Quake) are both WINAPI which is stdcall, not cdecl.

I've never really paid too much attention to how those 2 specific functions must use a different calling convention than the rest of the code.

No doubt because it is "interfacing" with the operating system, just like how Windows API calls are WINAPI calling convention.