Mime-Version: 1.0
Message-Id: <p05210609baffd3a79cfb@[207.213.214.37]>
In-Reply-To: <20030601140602.GA3641@work.bitmover.com>
References: <1054446976.19557.23.camel@spc>
 <20030601132626.GA3012@work.bitmover.com>
 <20030601134942.GA10750@alpha.home.local>
 <20030601140602.GA3641@work.bitmover.com>
Date: Sun, 1 Jun 2003 09:04:22 -0700
To: linux-kernel@vger.kernel.org
From: Jonathan Lundell <linux@lundell-bros.com>
Subject: Re: Question about style when converting from K&R to ANSI C.
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 945
Lines: 25

At 7:06am -0700 6/1/03, Larry McVoy wrote:
>It may be just what you are used to but I also find that when reading lots
>of code it is nice to have it look like
>
>return type
>function_name(args)
>
>because the function_name() stands out more, it's always at the left side so
>I tend to parse it a little more quickly.

The reason I've liked this format is that it gives me a quick and 
universal way to find *specific* functions with vi or grep, by 
searching for "^function_name(".

I'm less concerned with global function searches; there I don't mind 
the overhead of more sophisticated tools.

When we're done with this thread, perhaps we can return to endian arguments....
-- 
/Jonathan Lundell.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/