Date: Tue, 18 Jul 2000 08:17:33 +0930 From: Greg Lehey <grog@lemis.com> To: Ben Smithurst <ben@FreeBSD.org>, Marcel Moolenaar <marcel@cup.hp.com> Cc: Christopher Masto <chris@netmonger.net>, 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> In-Reply-To: <20000717132026.K84045@strontium.scientia.demon.co.uk> 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>
index | next in thread | previous in thread | raw e-mail
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
help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000718081733.P26231>