Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sat, 29 Dec 2001 08:02:11 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sat, 29 Dec 2001 08:01:58 -0500 Received: from garrincha.netbank.com.br ([200.203.199.88]:54535 "HELO netbank.com.br") by vger.kernel.org with SMTP id ; Sat, 29 Dec 2001 08:01:47 -0500 Date: Sat, 29 Dec 2001 11:01:29 -0200 (BRST) From: Rik van Riel X-X-Sender: To: Linus Torvalds Cc: Alan Cox , , Legacy Fishtank , Dave Jones , "Eric S. Raymond" , Marcelo Tosatti , , Subject: Re: State of the new config & build system In-Reply-To: Message-ID: X-spambait: aardvark@kernelnewbies.org X-spammeplease: aardvark@nl.linux.org MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 28 Dec 2001, Linus Torvalds wrote: > Having per-function comment blocks, in contrast, makes sense to have > inline: > > - you read the comment when you read the function > - you might even update the comment when you update the function > - you have a reasonable 1:1 relationship. Personally I'd like to see each C file have a header like this too, describing in a few lines what the functions in this file are supposed to do. This should make it easier for people to figure out not just what each C file is about, but also if they should spend their time wading through this particular C file when in search of some piece of code. regards, Rik -- Shortwave goes a long way: irc.starchat.net #swl http://www.surriel.com/ http://distro.conectiva.com/ - 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/