Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!linus!philabs!cmcl2!seismo!caip!nike!cad!pavepaws!keppel
From: keppel@pavepaws.berkeley.edu (David Keppel)
Newsgroups: net.lang,net.lang.c
Subject: Good C Style
Message-ID: <547@cad.BERKELEY.EDU>
Date: Mon, 9-Jun-86 22:26:34 EDT
Article-I.D.: cad.547
Posted: Mon Jun  9 22:26:34 1986
Date-Received: Thu, 12-Jun-86 01:24:08 EDT
Sender: news@cad.BERKELEY.EDU
Reply-To: keppel@pavepaws.UUCP (David Keppel)
Organization: CAD Group, U.C. Berkeley
Lines: 22
Keywords: style
Xref: linus net.lang:2212 net.lang.c:8576
Disorganization: University of California, Berkeley


	Just for the fun of it ("he'z a zick man, doktor"... :-) I'm
    rewriting part of the _Indian_Hill_C_Style_and_Coding_Standards_as
    amended_for_U_of_T_Zoology_UNIX_" document.  For those of you who
    haven't seen the document, it is a very compleat [sic] guide to
    readable, portable, functional code.

	Having seen numerous discussions about parts of this on the net,
    I am curious as to how people code, and as such I am soliciting
    submissions:

    o  Style conventions you make in coding
    o  Reasons for your conventions (if you feel a need to justify yourself :-)
    o  Conventions that you can't stand to read (;-)
    o  Small samples of actual code

	Please reply directly to me and *please* don't post it to the
    net!  If you are interested in the (semi)final results, I will send
    me mail & I will give you a roff-able copy when I'm done.

    :-D avid  K eppel				    ..!ucbvax!pavepaws!keppel
		"Learning by Osmosis: Gospel in, Gospel out"