Xref: utzoo comp.unix.wizards:7507 comp.lang.c:8786
Path: utzoo!utgpu!water!watmath!clyde!att-cb!att-ih!pacbell!ames!ncar!noao!arizona!lm
From: lm@arizona.edu (Larry McVoy)
Newsgroups: comp.unix.wizards,comp.lang.c
Subject: Re: Wanted: C Coding Standards Info
Message-ID: <4662@megaron.arizona.edu>
Date: 3 Apr 88 04:47:39 GMT
References: <355@stag.UUCP> <340@soleil.megatest.UUCP> <448@rabbit1.UUCP>
Reply-To: lm@megaron.arizona.edu (Larry McVoy)
Organization: University of Arizona, Tucson
Lines: 20

In article <448@rabbit1.UUCP> robert@rabbit1.UUCP (Robert Oliver) writes:
>In addition to the info Dave suggested in his followup article, you might try:
>
>"Portable C and Unix System Programming" by J.E.Lapin
>Prentice-Hall 
>
>I'll say no more, since it was written here.

I bought and read this about a year ago.  It's ok, not great.  

The best way I know to gain coding style (term used loosely) is to work on
kernel code for a while.  it's got a style that a lot of people hate but one
that many come to know and love after a few years of experience.  (I hate
comments for the most part, when there are a lot of them they're almost 
always wrong.  Not true in the kernel, but then there aren't a lot of 
comments either....)
-- 
"These aren't my thoughts, they're my cat walking on the keyboard."

Larry McVoy	lm@arizona.edu or ...!{uwvax,sun}!arizona.edu!lm