Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!mit-eddie!ll-xn!ames!sdcsvax!ucsdhub!hp-sdd!hplabs!hpda!hpcupt1!hpisod2!decot
From: decot@hpisod2.HP.COM (Dave Decot)
Newsgroups: comp.lang.c
Subject: Re: for vs. while (was: Re: documentation standards........)
Message-ID: <2550032@hpisod2.HP.COM>
Date: Tue, 10-Nov-87 22:01:08 EST
Article-I.D.: hpisod2.2550032
Posted: Tue Nov 10 22:01:08 1987
Date-Received: Sat, 14-Nov-87 02:26:51 EST
References: <1987Oct25.234440.16608@sq.uucp>
Organization: Hewlett Packard, Cupertino
Lines: 26

> >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()
> {
> }

Use of the program ctags(1) makes this unnecessary, keeps track of
which function is in which file for easy jumping, and works even
for code imported from elsewhere that did not use this convention.

Dave Decot
hpda!decot