Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 22 Jul 2008 07:50:30 -0700
From:      "Garrett Cooper" <gcooper@FreeBSD.org>
To:        freebsd-standards@freebsd.org, freebsd-bugs@freebsd.org, gcooper@freebsd.org
Subject:   Re: bin/125855: sh(1) allows for multiline, non-escaped control structures (and thus isn't POSIX compliant)
Message-ID:  <364299f40807220750lc12de99y33ff05da97fb4243@mail.gmail.com>
In-Reply-To: <200807221303.m6MD3bas000198@lurza.secnetix.de>
References:  <200807220836.m6M8av6k080061@freefall.freebsd.org> <200807221303.m6MD3bas000198@lurza.secnetix.de>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jul 22, 2008 at 6:03 AM, Oliver Fromme <olli@lurza.secnetix.de> wrote:
> Actually I think that both bash's and sh's behaviour is
> correct.  As far as I can see in the refrenced standard
> sections, there is no requirement that there must be no
> newline character after the reserved word "!".  It seems
> to be unspecified.
>
> FWIW, Solaris' POSIX shell (/bin/ksh and /usr/xpg4/bin/sh)
> allows a newline character, so it behaves the same as our
> /bin/sh.  (Note that Solaris' /bin/sh is intentionally not
> a POSIX shell, it doesn't know "!" at all.)
>
> Best regards
>   Oliver

Oliver,
     Ok. That's what I thought when I was reading the OpenGroup spec
again. It's a bit confusing because I think this is a gray area...
     I'll see what the POSIX folks say.
Thanks,
-Garrett



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?364299f40807220750lc12de99y33ff05da97fb4243>