Date: Wed, 16 Oct 2002 09:00:03 -0700 (PDT) From: Garrett Wollman <wollman@lcs.mit.edu> To: freebsd-bugs@FreeBSD.org Subject: bin/44142: /bin/sh does not support 'command1 & && command2' syntax, which is REQUIRED by POSIX Message-ID: <200210161600.g9GG03Nk042760@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR bin/44142; it has been noted by GNATS. From: Garrett Wollman <wollman@lcs.mit.edu> To: Alexandr Kovalenko <never@nevermind.kiev.ua> Cc: FreeBSD-gnats-submit@FreeBSD.ORG Subject: bin/44142: /bin/sh does not support 'command1 & && command2' syntax, which is REQUIRED by POSIX Date: Wed, 16 Oct 2002 11:55:42 -0400 (EDT) <<On Wed, 16 Oct 2002 17:16:54 +0300 (EEST), Alexandr Kovalenko <never@nevermind.kiev.ua> said: > /bin/sh does not support 'command1 & && command2' syntax, which is REQUIRED by POSIX: Your interpretation is erroneous. The grammar takes precedence over the textual description of the syntax, and the grammar is quite clear: complete_command : list separator | list ; list : list separator_op and_or | and_or ; and_or : pipeline | and_or AND_IF linebreak pipeline | and_or OR_IF linebreak pipeline ; The pseudo-syntax `command1 &' can only be resolved by the `list' production in the grammar. The `&&' and `||' operators take pipelines, and not lists, as operands. See XCU6 page 58. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200210161600.g9GG03Nk042760>