From owner-freebsd-current  Mon Sep  2 14:11:40 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id OAA13118
          for current-outgoing; Mon, 2 Sep 1996 14:11:40 -0700 (PDT)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA13112
          for <freebsd-current@FreeBSD.org>; Mon, 2 Sep 1996 14:11:35 -0700 (PDT)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA03052; Mon, 2 Sep 1996 14:09:51 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199609022109.OAA03052@phaeton.artisoft.com>
Subject: Re: Anyone mind if I remove the following braindamage from test(1)?
To: jkh@time.cdrom.com (Jordan K. Hubbard)
Date: Mon, 2 Sep 1996 14:09:50 -0700 (MST)
Cc: joerg_wunsch@uriah.heep.sax.de, freebsd-current@FreeBSD.org,
        bde@zeta.org.au
In-Reply-To: <2920.841647977@time.cdrom.com> from "Jordan K. Hubbard" at Sep 2, 96 00:06:17 am
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

> I'd expect that to hold true only if the argument was not a flag
> argument which required a parameter, then I'd expect it to puke.  This
> would also help to quickly find instances where you'd undefined a
> necessary variable in the source tree, instead of giving a cryptic
> error message like:  ``usage: rm [-f | -i] [-dPRr] file ...''

I agree; a flag isn't an argument, it's a flag.


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.