Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site dataio.UUCP
Path: utzoo!watmath!clyde!cbosgd!ihnp4!houxm!mtuxo!mtunh!mtung!mtunf!ariel!vax135!cornell!uw-beaver!uw-june!entropy!dataio!bjorn
From: bjorn@dataio.UUCP (Bjorn Benson)
Newsgroups: net.lang.c
Subject: Re: more about programming style
Message-ID: <739@dataio.UUCP>
Date: Wed, 31-Jul-85 11:52:45 EDT
Article-I.D.: dataio.739
Posted: Wed Jul 31 11:52:45 1985
Date-Received: Sat, 3-Aug-85 03:46:34 EDT
References: <732@dataio.UUCP> <261@brl-tgr.ARPA>
Reply-To: bjorn@dataio.UUCP (Bjorn Benson)
Organization: Data I/O Corp., Redmond WA
Lines: 16

In article <261@brl-tgr.ARPA> gwyn@brl-tgr.ARPA (Doug Gwyn <gwyn>) writes:
>> char (*f[6])();	/* <array of><pointer to><function returning><char> */
>
>The comment provides no useful information.  Any experienced C
>programmer should be able to read the declaration as fast as he
>can read the comment, maybe faster.  

Right, any PROGRAMMER can read it faster.  However some of us who spend
more time designing, testing and documenting than actually writing
code find terse C a bit cryptic.  As an ENGINEER, I like explict
correct comments, as they really help when I re-read code.

Don't get me wrong, I like C's terseness when I am writing and actively
editting code but later in the development cycle it can be annoying...

					Bjorn Benson