One can argue that portability and "well-written" code go hand-in-hand. Loosely defined, well-written code is one that is "easy" to understand and "easy" to maintain, and there are several style guides in the public domain expressing various views on the subject.
Besides the style guide mentioned in the foreword, there are a few more that can be obtained in cs.toronto.edu [128.100.1.65] in ~ftp/doc/programming. We also recommend standards.text from the Free Software Foundation which can be found in various sites, e.g., prep.ai.mit.edu [18.71.0.38] in ~ftp/pub/gnu.
For those who have access to the Usenet newsgroup comp.lang.c, we highly recommend reading the Frequently Asked Questions List (known as the FAQL) which is posted at the beginning of every month.
contents
General Guidelines
Acknowledgements