Xref: utzoo alt.religion.computers:2031 comp.lang.c:33608
Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!noao!ncar!elroy.jpl.nasa.gov!sdd.hp.com!zaphod.mps.ohio-state.edu!samsung!olivea!mintaka!spdcc!ima!dirtydog!karl
From: karl@ima.isc.com (Karl Heuer)
Newsgroups: alt.religion.computers,comp.lang.c
Subject: Re: Argument declaration style (Was: ANSI C prototypes)
Message-ID: <1990Nov10.051313.18888@dirtydog.ima.isc.com>
Date: 10 Nov 90 05:13:13 GMT
References: <BZS.90Nov6205843@world.std.com> <930@demott.COM> <1990Nov7.181615.11154@craycos.com>
Sender: news@dirtydog.ima.isc.com (NEWS ADMIN)
Reply-To: karl@ima.isc.com (Karl Heuer)
Followup-To: alt.religion.computers
Organization: Interactive Systems
Lines: 18

In article <1990Nov7.181615.11154@craycos.com> pmk@craycos.com (Peter Klausler) writes:
>I also like ANSI prototypes, but use this style:
>	void
>	foo (int x, int y) {
>	}
>so that the function name always appears in column 1.

Personally, I think the existence of functions like "signal" demonstrates that
this isn't the way God intended functions to be written. :-)

The only advantage I've heard for this is that it makes it easy to find the
function with grep.  I'm willing to endure the hardship of using egrep instead
of grep in exchange for the benefit of having it print out the entire
declaration including type when it does find it.  Besides, my egrep pattern
works on macros too.

Karl W. Z. Heuer (karl@ima.isc.com or uunet!ima!karl), The Walking Lint
Followups to alt.religion.computers.