From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <50b92b0d59c434b68697d47b88788263@plan9.bell-labs.com> From: presotto@plan9.bell-labs.com To: 9fans@cse.psu.edu Subject: Re: [9fans] samuel MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="upas-ffkzyusmgksqzvfvbsptoajpuh" Date: Sun, 10 Mar 2002 16:42:15 -0500 Topicbox-Message-UUID: 630286aa-eaca-11e9-9e20-41e7f4b1d025 This is a multi-part message in MIME format. --upas-ffkzyusmgksqzvfvbsptoajpuh Content-Disposition: inline Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Actually, I started using the style before I started using grep to find functions. The most important part of the declaration for me is the function name. The rest is a description of what that name represents which I can find pretty easily once I find the function in my visual field. Anything that hides it from me, I find distracting. The big difference for me when I started coding on plan 9 was putting the formal parameters on the same line as the function name. I used to separate them onto subesequent lines, one per line with comments. However, I bent to local practice on that. However, if you don't like it, I see no reason why you should do it. I automaticly reformat other people's code to meet my particular nuances before I try to understand it, especially if it's rather complex. I'm not quite sure why anyone is railing against samuel; if samuel helps some people manage code a bit better, use it. I prefer the plumber to do similar things since it's not oriented to a single editor. --upas-ffkzyusmgksqzvfvbsptoajpuh Content-Type: message/rfc822 Content-Disposition: inline Received: from plan9.cs.bell-labs.com ([135.104.9.2]) by plan9; Sun Mar 10 15:15:14 EST 2002 Received: from mail.cse.psu.edu ([130.203.4.6]) by plan9; Sun Mar 10 15:15:13 EST 2002 Received: from psuvax1.cse.psu.edu (psuvax1.cse.psu.edu [130.203.30.6]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id 0237319980; Sun, 10 Mar 2002 15:15:07 -0500 (EST) Delivered-To: 9fans@cse.psu.edu Received: from mta5-rme.xtra.co.nz (mta5-rme.xtra.co.nz [210.86.15.138]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id 5972119992 for <9fans@cse.psu.edu>; Sun, 10 Mar 2002 15:14:55 -0500 (EST) Received: from MERCURY ([210.55.57.168]) by mta5-rme.xtra.co.nz with SMTP id <20020310201454.HWFW25716.mta5-rme.xtra.co.nz@MERCURY> for <9fans@cse.psu.edu>; Mon, 11 Mar 2002 09:14:54 +1300 Message-Id: <3.0.6.32.20020311091707.00998010@pop3.clear.net.nz> X-Sender: mbml/andrew@pop3.clear.net.nz X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) To: 9fans@cse.psu.edu From: Andrew Simmons Subject: Re: [9fans] samuel In-Reply-To: <251acfe686a4582fc8f6978c5b82db07@plan9.bell-labs.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: 9fans-admin@cse.psu.edu Errors-To: 9fans-admin@cse.psu.edu X-BeenThere: 9fans@cse.psu.edu X-Mailman-Version: 2.0.8 Precedence: bulk Reply-To: 9fans@cse.psu.edu List-Help: List-Id: Fans of the OS Plan 9 from Bell Labs <9fans.cse.psu.edu> List-Archive: Date: Mon, 11 Mar 2002 09:17:07 +1300 > >Dinosaurs didn't have grep. > They do now. Sorry, that was really cheap, but I do think Alex has a point. It ties in with a query I made re coding layout. If people lay out function definitions with the return type on a separate line because they find it makes them easier to read, then fine. If, however, they find that style ugly and distracting (and maybe I'm the only one who does) but do it anyway, because it allows then to find the function definition using grep, then maybe the tail has started to wag the dog a little, and it's time to consider extending the toolkit? --upas-ffkzyusmgksqzvfvbsptoajpuh--