From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-14) on finch.gentoo.org X-Spam-Level: * X-Spam-Status: No, score=1.1 required=5.0 tests=DATE_IN_PAST_12_24,DMARC_NONE, INVALID_DATE,MAILING_LIST_MULTI autolearn=no autolearn_force=no version=4.0.0 Received: from mail11.speakeasy.net ([216.254.0.211]) by cvs.gentoo.org with esmtp (Exim 3.30 #1) id 162fTt-0007rr-00 for gentoo-dev@cvs.gentoo.org; Sat, 10 Nov 2001 14:16:01 -0700 Received: (qmail 58959 invoked from network); 10 Nov 2001 21:15:33 -0000 Received: from unknown (HELO yde.flatmonk.org) ([66.92.103.162]) (envelope-sender ) by mail11.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 10 Nov 2001 21:15:33 -0000 Received: from agriffis by yde.flatmonk.org with local (Exim 3.33 #1 (Debian)) id 162fSh-00077q-00 for ; Sat, 10 Nov 2001 16:14:47 -0500 From: Aron Griffis To: gentoo-dev@cvs.gentoo.org Subject: Re: [gentoo-dev] Re: All Developers! Message-ID: <20011110161447.A20091@yde.flatmonk.org> Mail-Followup-To: gentoo-dev@cvs.gentoo.org References: <1005392055.10442.2.camel@zoidberg> <20011110165601.1b5869a1.karltk@prosalg.no> <1005406570.28610.0.camel@zoidberg> <3BED57AA.4030301@acm.org> <20011110112442.E16660@cvs.gentoo.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20011110112442.E16660@cvs.gentoo.org> User-Agent: Mutt/1.3.22.1i X-Mailer: Mutt http://www.mutt.org/ X-Editor: Vim http://www.vim.org/ Sender: gentoo-dev-admin@cvs.gentoo.org Errors-To: gentoo-dev-admin@cvs.gentoo.org X-BeenThere: gentoo-dev@cvs.gentoo.org X-Mailman-Version: 2.0 Precedence: bulk Reply-To: gentoo-dev@cvs.gentoo.org List-Help: List-Post: List-Subscribe: , List-Id: Gentoo Linux development list List-Unsubscribe: , List-Archive: Date: Sat Nov 10 14:17:02 2001 X-Original-Date: Sat, 10 Nov 2001 16:14:47 -0500 X-Archives-Salt: 0ccac9bc-d25c-441e-b229-7d3c8fe747ca X-Archives-Hash: d28d466459289f2ad01e971533893a1e Daniel Robbins wrote: [Sat Nov 10 2001, 01:24:42PM EST] > 1) Use one tab per indent > > 2) Put comments on separate lines > > 3) Avoid using "/" line continuation characters and use long lines instead. I don't care about 1 and 2, but I agree with Chouser about long lines. I don't mind terribly when I have to edit an existing ebuild with long lines, but *please* don't ask me to write them like that. Continuations can make the code more understandable when used appropriately. And it's easy to write continuations that don't have any problem with developers' tabbing preferences: ./configure \ --prefix=/usr \ --mandir=/usr/share/man \ --infodir=/usr/share/info This might be considered overuse of line continuations, but it makes my point; the code is readable, fits in a standard terminal, and has no issues with tabs. Aron