Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!lsuc!ncrcan!brian
From: brian@ncrcan.UUCP
Newsgroups: comp.lang.c
Subject: Re: documentation standards........
Message-ID: <367@ncrcan.Toronto.NCR.COM>
Date: Thu, 5-Nov-87 11:29:32 EST
Article-I.D.: ncrcan.367
Posted: Thu Nov  5 11:29:32 1987
Date-Received: Sun, 8-Nov-87 06:56:08 EST
References: <9897@brl-adm.ARPA> <913@sugar.UUCP> <6606@brl-smoke.ARPA>
Reply-To: brian@ncrcan.Toronto.NCR.COM ()
Organization: NCR Canada Ltd., Mississauga, Ontario
Lines: 26

In article <6606@brl-smoke.ARPA> gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>) writes:
>In article <913@sugar.UUCP> peter@sugar.UUCP (Peter da Silva) writes:
>>is really irrelevant. It would be nice if you can indent the body of your
>>functions, though:
>
>Quite right, discussion of personal stylistic preferences is a waste
>of network bandwidth.  On the other hand, there can be practical
>reasons for some aspects of coding style.  For example, if identifiers
>for function definitions occur against the left margin but most other
>text is indented, then it is easy with most text editors to quickly
>jump to the beginning of any function whose name is known, or to
>grep a set of sources to find out which one defines the function (as
>opposing to calling it).

Which is why all my functions are declared as follows:

int 
myfunction()
{
}

and not:

int myfunction()
{
}