Modern C for C++ Peeps

> Enable all warnings! The trouble I've run into with that is different compilers have different warnings, sometimes they are mutually contradictory, so it is not possible to have portable code that doesn't trigger warnings in one compiler or another. I.e. the general problem with warnings is the language gets balkanized into multiple competing and incompatible dialects. What should happen is to carefully examine the warnings, and adopt the best into the language Standard as errors. For example: if (a…

I tend to disagree that RAII is used only used for memory. We've RAII wrappers for locks, file handles etc. all the time in our code base. Also it's impractical to only have POD structs i.e. structs with no pointer pointing to the free store. Good otherwise. Nice colours and theming though :)

> Wrap your structs in a typedef I tend to disagree. Unless you are providing an API for third-party use and want to make your data types opaque to callers, do not ever use typedef with structs and pointers. A declaration like "struct foo *f" tells you two things - f itself is a pointer, and the pointed-to value is not a scalar (i.e. has named members). The "_t" suffix idiom is predominantly used by the standard library for integral…