From owner-freebsd-standards@FreeBSD.ORG Thu Jun 28 22:20:13 2012 Return-Path: Delivered-To: freebsd-standards@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9CEAA106564A for ; Thu, 28 Jun 2012 22:20:13 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 843688FC0C for ; Thu, 28 Jun 2012 22:20:13 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q5SMKDMi069885 for ; Thu, 28 Jun 2012 22:20:13 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q5SMKDVs069884; Thu, 28 Jun 2012 22:20:13 GMT (envelope-from gnats) Date: Thu, 28 Jun 2012 22:20:13 GMT Message-Id: <201206282220.q5SMKDVs069884@freefall.freebsd.org> To: freebsd-standards@FreeBSD.org From: "Ronald F. Guilmette" Cc: Subject: Re: bin/169500: /bin/expr improperly requires forward slash to be escaped X-BeenThere: freebsd-standards@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "Ronald F. Guilmette" List-Id: Standards compliance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Jun 2012 22:20:13 -0000 The following reply was made to PR bin/169500; it has been noted by GNATS. From: "Ronald F. Guilmette" To: Garrett Wollman Cc: freebsd-gnats-submit@freebsd.org Subject: Re: bin/169500: /bin/expr improperly requires forward slash to be escaped Date: Thu, 28 Jun 2012 15:11:55 -0700 In message <201206280136.q5S1aOQO093902@hergotha.csail.mit.edu>, you wrote: >In article <20120627214105.A1EA35081B@segfault.tristatelogic.com>, >rfg@tristatelogic.com writes: > >>According to my reading of Sections 2.8.3.1.1 and 2.8.3.1.2 of the ANSI/IEEE >>standard 1003.2, a forward slash character (/) is an "ordinary" basic >>regular expression (BRE) character, and as such can be used in a BRE alone >>to match itself. > >IEEE Std.1003.2 was obsoleted by the publication of IEEE >Std.1003.1-2001; your reference is at least fifteen years old. Yes. My bad. Sorry. (These publications are quite expensive, as you may know, and thus, I have not updated mine in quite some time.) >>As far as I can tell, backslash-escaping of this specific character >>should not be required within BREs. > >Nothing to do with the BRE-ness. As the 2001 edition of the standard >states (page 429, lines 16598-16599): > > A string argument is an argument that cannot be identified as > an integer argument or as one of the expression operator > symbols shown in the OPERANDS section. Humm... OK. How do I retract my PR?