Path: csiph.com!goblin2!goblin1!goblin.stu.neva.ru!usenet.stanford.edu!not-for-mail
From: Piotr Grzybowski <narsil.pl@gmail.com>
Newsgroups: gnu.bash.bug
Subject: Re: ./parse.y: warning: 1 shift/reduce conflict [-Wconflicts-sr]
Date: Wed, 27 Jun 2018 16:33:05 +0200
Lines: 39
Approved: bug-bash@gnu.org
Message-ID: <mailman.2619.1530109999.1292.bug-bash@gnu.org>
References: <5260CA01-40C6-41A8-A858-760C84CB8FBB@gmail.com> <608b0390-0483-fede-f1f7-d6fad57d5735@case.edu>
NNTP-Posting-Host: lists.gnu.org
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
To: bug-bash <bug-bash@gnu.org>
Envelope-to: bug-bash@gnu.org
In-Reply-To: <608b0390-0483-fede-f1f7-d6fad57d5735@case.edu>
Precedence: list
Xref: csiph.com gnu.bash.bug:14281


On 27 Jun 2018, at 14:57, Chet Ramey wrote:

> On 6/27/18 6:59 AM, Piotr Grzybowski wrote:
>=20
>> +function_newline_list: '(' ')' | function_newline_list '\n'
>> +       ;
>> +
>=20
> This would appear to allow constructs like
>=20
> foo()
> () ()
> {
> 	function body
> }

only by the look of things ;-) (thats what I meant in P.S.) actually =
those tokens are not allowed:

bash-5.0$ cat /tmp/m.sh
foo()
() ()
{
        function body
}

bash-5.0$ . /tmp/m.sh
bash: /tmp/m.sh: line 2: syntax error near unexpected token `)'
bash: /tmp/m.sh: line 2: `() ()'

 I am sure function_newline_list can be rewritten in a better way =
though.

cheers,
pg