Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site brl-tgr.ARPA
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!genrad!panda!talcott!harvard!seismo!brl-tgr!tgr!gwyn@Brl.ARPA
From: gwyn@Brl.ARPA (VLD/VMB)
Newsgroups: net.lang.c
Subject: Re:  long names in C programs
Message-ID: <10814@brl-tgr.ARPA>
Date: Sat, 18-May-85 22:44:47 EDT
Article-I.D.: brl-tgr.10814
Posted: Sat May 18 22:44:47 1985
Date-Received: Sun, 19-May-85 23:51:26 EDT
Sender: news@brl-tgr.ARPA
Lines: 11

Sounds like you're not exerting enough control over the contract
C programmers.  Plum-Hall publishes some excellent guideline documents
that you could require conformance to.  For one's own purposes,
Harbison & Steele do a good job of making recommendations for
portability in their "C: A Reference Manual".

I agree that the default behavior of a C programmer should be to
code portably, except when there is a demonstrable problem doing so.
Unfortunately, most recent college grads have not been exposed to a
wide enough range of systems to really understand what the portability
issues are, so they should rely on guidelines published by those who do.