From owner-freebsd-standards@FreeBSD.ORG Tue Sep 7 18:45:18 2004 Return-Path: Delivered-To: freebsd-standards@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5A66F16A50E; Tue, 7 Sep 2004 18:45:18 +0000 (GMT) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [128.30.28.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1056543D3F; Tue, 7 Sep 2004 18:45:18 +0000 (GMT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: from khavrinen.lcs.mit.edu (localhost [IPv6:::1]) by khavrinen.lcs.mit.edu (8.12.9/8.12.9) with ESMTP id i87IjB8g099897 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK CN=khavrinen.lcs.mit.edu issuer=SSL+20Client+20CA); Tue, 7 Sep 2004 14:45:11 -0400 (EDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.12.9/8.12.9/Submit) id i87IjAu6099894; Tue, 7 Sep 2004 14:45:10 -0400 (EDT) (envelope-from wollman) Date: Tue, 7 Sep 2004 14:45:10 -0400 (EDT) From: Garrett Wollman Message-Id: <200409071845.i87IjAu6099894@khavrinen.lcs.mit.edu> To: Harti Brandt In-Reply-To: <20040907163809.M20166@beagle.kn.op.dlr.de> References: <1094566670.80264.78.camel@localhost> <20040907163809.M20166@beagle.kn.op.dlr.de> X-Spam-Score: -19.8 () IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES,REPLY_WITH_QUOTES X-Scanned-By: MIMEDefang 2.37 cc: FreeBSD Standards cc: Dan Nelson Subject: Re: /bin/test asdf -ge 0 X-BeenThere: freebsd-standards@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Standards compliance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Sep 2004 18:45:18 -0000 < said: > I just checked the TC1 of Posix and it doesn't say anything in the > description of test about this. Also the 'utility argument syntax' section > talks only about range errors of numeric operands in point 6. So the > behaviour seems to be unspecified. It's not clear whether this is an > oversight or intended. I agree. I believe that an interpretation request would receive the "the standard is silent and no conformance distinction can be made" (and therefore FreeBSD's implementation is not incorrect). It's instructive to contrast the description of expr(1), where the standard makes it very clear what constitutes a number. -GAWollman