This document is a modified version of a document from a committee formed at AT&T’s Indian Hill labs to establish a common set of coding standards and recommendations for the Indian Hill community.Good style should encourage consistent layout, improve portability, and reduce errors. This work does not cover functional organization, or general issues such as the use
of gotos.Experience and informed judgement count for much.
Programmers who encounter unusual situations should consult either experienced C programmers or code written by experienced C programmers (preferably following these rules).
