Hacker News Reader

Best of both worlds: use static analysis to ensure the header is included?

gcc has a -include option, so this can be done once in the Makefile and get the benefit everywhere (unless you’re being clever).

I remember visual studio having an option to force include a file, surely something like that would exist for other toolchains

You don't need fancy static analysis. You can find out whether the banned functions are called just by inspecting the compiled object file. Add it to the build step and done.