Path: csiph.com!goblin1!goblin.stu.neva.ru!usenet.stanford.edu!not-for-mail
From: moosotc@gmail.com
Newsgroups: gnu.bash.bug
Subject: Re: Function definitions
Date: Mon, 26 Feb 2018 18:24:11 +0300
Lines: 37
Approved: bug-bash@gnu.org
Message-ID: <mailman.9754.1519658661.27995.bug-bash@gnu.org>
References: <877er0qbb7.fsf@gmail.com> <3f544894-f4e2-4c51-9202-6a6e92ae8ebb@case.edu>
NNTP-Posting-Host: lists.gnu.org
Mime-Version: 1.0
Content-Type: text/plain
Cc: bug-bash@gnu.org
To: Chet Ramey <chet.ramey@case.edu>
Envelope-to: bug-bash@gnu.org
In-Reply-To: <3f544894-f4e2-4c51-9202-6a6e92ae8ebb@case.edu> (Chet Ramey's message of "Mon, 26 Feb 2018 09:20:55 -0500")
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (gnu/linux)
Precedence: list
Xref: csiph.com gnu.bash.bug:13752

Chet Ramey <chet.ramey@case.edu> writes:

> On 2/26/18 5:45 AM, moosotc@gmail.com wrote:
>
>> Bash Version: 4.4
>> Patch Level: 19
>> Release Status: release
>> 
>> Description:
>>         Bash rejects valid function definitions
>> 
>> Repeat-By:
>> 
>> $ func() true
>> bash: syntax error near unexpected token `true'
>
> Yes, bash requires that function bodies be compound commands, as the Posix
> grammar specifies.
>
>> # Variant#2
>> $ func() { true }
>>> ^C
>
> This is not a valid compound command. To be recognized as a reserved word,
> and end the group command, the close brace must appear in a context where
> a reserved word is valid. The argument to a simple command is not such a
> place.

Thank you for an explanation. My takeaway is that most, if not all,
[kaz]sh descendants[1] allow something that IEEE Std 1003.1-2008, 2016
Edition doesn't.

[1] dash,busybox,mksh,zsh

-- 
mailto:moosotc@gmail.com