Well, the GNU Coding Standards are listed, and if GCC is any indication, no one follows them, so we can probably surmise that the GNU ones are less awesome than any other C ones provided.
The GNU guide has some gems in it.
1989 Standard C is widespread enough now that it is ok to use its features in programs.
If you do support Windows, please do not abbreviate it as “win”. In hacker terminology, calling something a “win” is a form of praise. You’re free to praise Microsoft Windows on your own if you want, but please don’t do this in GNU packages. Instead of abbreviating “Windows” to “win”, you can write it in full or abbreviate it to “woe” or “w”.
If two guidelines have conflicting rules, how do I determine which is most awesome?
Well, the GNU Coding Standards are listed, and if GCC is any indication, no one follows them, so we can probably surmise that the GNU ones are less awesome than any other C ones provided.
The GNU guide has some gems in it.
Perhaps we might start calling these “aw” lists to create some ambiguity.