How to C in 2016

[JasonX]

Love it: https://matt.sh/howto-c

[jitspoe]

Meanwhile, I'm too lazy to update my compiler (and don't want to risk breaking compatibility for some players), so I'm still using Visual Studio 2010, and half this stuff doesn't work.

[Baker]

Sounds the guy who wrote that "advice" is big into unportable code that depends on whose compiler you are using. Maybe that works for him, his environment, the projects he works on and the operating systems that matter to him and the compilers he uses and doesn't use.

Someone saying there is "the one true way" hasn't poked his head out of a hole enough to know that.

C is a thin veneer over assembly language.

More recent C standards have few truly useful features over older C, so sacrificing portability and compile backwards compatibility to be "modern" isn't a very good reason in a lot of cases. Case in point, SDL2 is C-89 compatible as an example.

[Spike]

baker, the only reason to stick to c89 is msvc, and even that is changing now - msvc2015 supposedly implements nearly the full c99 libc requirements (its missing a couple of twiddles, but I doubt you've ever used them).
so really, c89 is finally obsolete. its only the people using obsolete versions of microsoft's tool chains who still need to use it.

[Baker]

[Baker]

@spike --- does Visual Studio 2015 happen to have anonymous union support in C?

/If you know ...

[Spike]

older versions do, so I assume it must have.