Path: utzoo!attcan!uunet!oddjob!ncar!boulder!sunybcs!bingvaxu!leah!itsgw!batcomputer!cornell!rochester!ur-tut!pmjc
From: pmjc@ur-tut (Pam Arnold)
Newsgroups: comp.lang.misc
Subject: Re: Style rules for C shops
Message-ID: <2067@ur-tut.UUCP>
Date: 16 May 88 03:52:45 GMT
References: <12120@santra.UUCP> <1962@bgsuvax.UUCP> <12567@santra.UUCP> <4043@killer.UUCP> <12822@santra.UUCP>
Reply-To: pmjc@tut.cc.rochester.edu.UUCP (Pam Arnold)
Distribution: comp.lang.misc,comp.lang.c
Organization: Univ. of Rochester Computing Center
Lines: 15

In article <12822@santra.UUCP> nbo@hutcs.UUCP (Nassim Bouteldja) writes:
>In article <4043@killer.UUCP> loci@killer.UUCP (loci!clb) writes:
>>In article <12567@santra.UUCP>, news@santra.UUCP (news) writes:
>>> In article <1962@bgsuvax.UUCP> denbeste@bgsuvax.UUCP (William C. DenBesten) writes:
>>> >>The ideal solution

Two suggestions: wouldn't periodic code walk-throughs expose the people
who are violating the local coding standards? If I knew that my code was
going to be up on the wall every week, I would certainly make sure that
it was up to snuff in terms of style (and hopefully substance as well).

This one may beg the question, but if any shop is REALLY SERIOUS about
this sort of problem, why not switch to a more modern language, especially
one that is more tailored to the requirements of software engineering? For
example Modula-2 and Ada (no flames, just add your own to the list).