From owner-cvs-all Mon Jul 17 15:47:48 2000 Delivered-To: cvs-all@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 6CB5037B654; Mon, 17 Jul 2000 15:47:35 -0700 (PDT) (envelope-from grog@wantadilla.lemis.com) Received: (from grog@localhost) by wantadilla.lemis.com (8.9.3/8.9.3) id IAA87928; Tue, 18 Jul 2000 08:17:33 +0930 (CST) (envelope-from grog) Date: Tue, 18 Jul 2000 08:17:33 +0930 From: Greg Lehey To: Ben Smithurst , Marcel Moolenaar Cc: Christopher Masto , cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/share/man/man9 style.9 Message-ID: <20000718081733.P26231@wantadilla.lemis.com> References: <20000717113109.D52835@wantadilla.lemis.com> <20000716225410.A15022@netmonger.net> <20000717142018.D26231@wantadilla.lemis.com> <20000717132026.K84045@strontium.scientia.demon.co.uk> <39734383.12FCC14F@cup.hp.com> <200007162046.NAA80035@freefall.freebsd.org> <20000717113109.D52835@wantadilla.lemis.com> <20000716225410.A15022@netmonger.net> <20000717142018.D26231@wantadilla.lemis.com> <20000717132026.K84045@strontium.scientia.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <20000717132026.K84045@strontium.scientia.demon.co.uk> Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Monday, 17 July 2000 at 13:20:26 +0100, Ben Smithurst wrote: > Greg Lehey wrote: > >> I don't really care which we end up with, as long as we define them >> somewhere to avoid confusion. But it sounds good, modulo the typo >> that Chris picked up. I think I'd leave out "curly", too: we don't >> have any other type of brace. > > So the only thing you disagree about then is that "brackets" should > be changed to "square brackets". I almost agree -- the PR actually > suggested "square brackets", but Sheldon suggested just "brackets" > instead. > > There is an example just below this text anyway, which I think makes it > clear enough. But I don't mind changing "brackets" to "square brackets" > if enough people think it should be changed and no-one else objects. On Monday, 17 July 2000 at 10:33:55 -0700, Marcel Moolenaar wrote: > Ben Smithurst wrote: > >>> I don't really care which we end up with, as long as we define them >>> somewhere to avoid confusion. But it sounds good, modulo the typo >>> that Chris picked up. I think I'd leave out "curly", too: we don't >>> have any other type of brace. >> >> So the only thing you disagree about then is that "brackets" should >> be changed to "square brackets". I almost agree -- the PR actually >> suggested "square brackets", but Sheldon suggested just "brackets" >> instead. >> >> There is an example just below this text anyway, which I think makes it >> clear enough. But I don't mind changing "brackets" to "square brackets" >> if enough people think it should be changed and no-one else objects. > > Given the ambiguity, I think "square brackets" is preferrable. I feel > the same about "curly braces" instead of just "braces". I'm not talking about changing the terms, just defining them. Something like this would be a good idea: If the macro needs more than a single line, use braces ('{' and '}'). ... 1. Options without operands come first, in alphabetical order, inside a We already have something like this a little lower: A bar (`|') separates either-or options/arguments, and multiple op- tions/arguments which are specified together are placed in a single set of brackets. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message