* Do NOT use the GNU indentation style!
  Any code that isn't sanely indented will be reindented
  in a proper way.  This is NOT negotiable!
  
  `indent -kr -i8 -bs -ncs -l79' is a good start, but you'll probably
  have to do some manual work as well, since indent doesn't know about
  everything, and seems to mishandle labels in a gross way...

  And remember, despite what some may believe, a proper terminal window is
  still 80 characters wide.  Always try to keep your code within that
  width if at all possible, but don't break up code just for the sake of
  keeping the sacred 80-character rule, use common sense.  If uncertain,
  have a look at existing code.

* The rest of the GNU standards are pretty sane, read them.

* Don't use floating point math.  This makes things easier for people
  on platforms with weak or no floating-point support.

* GNU-standards says that manual-pages are not essential.  Ignore that
  heresy.  Write decent manual-pages, or at least ask someone else to
  do it for you.  Everything in this suite of programs should have
  proper manual-pages, including file-formats, and (in the future)
  library-functions.  Info-pages are great, but they are a complement
  to manual-pages, not a replacement.

* Stay away from GCC extensions.  If you feel that they are needed,
  you are probably doing something wrong.  C99 is perfectly fine to use,
  though.

* Use /* */ for comments, // for temporary comments (such as FIXME's),
  and #if 0 + #endif for commenting out sections
