From: Martin Vaeth <martin@mvath.de>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Anyone else having a problem with bash?
Date: Mon, 13 Jul 2015 14:00:54 +0000 (UTC) [thread overview]
Message-ID: <mo0gam$1ps$2@ger.gmane.org> (raw)
In-Reply-To: 55a38749.kvL+R6szt5h0VGWr%Joerg.Schilling@fokus.fraunhofer.de
Joerg Schilling <Joerg.Schilling@fokus.fraunhofer.de> wrote:
>
> bash vs. POSIX, as bash tried to ignore long existing
> rules just because the bash maintainer did not understand them.
Are there really several? I know only one such example:
bash insists on compound commands ("{ ... }" or "( ... )")
for the function body while according to POSIX also
non-compound commmands can form the body, e.g.
hello() echo "hello world"
is a valid function definition according to POSIX
(and thus works in dash or also zsh) but not in bash:
Rumors say that the bash maintainer intentionally
excluded this due to some misinterpretation of the
POSIX formulation.
next prev parent reply other threads:[~2015-07-13 14:05 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-06 17:01 [gentoo-user] Anyone else having a problem with bash? walt
2015-07-06 17:18 ` Alexander Kapshuk
2015-07-06 19:07 ` [gentoo-user] " »Q«
2015-07-06 20:43 ` Alex Thorne
2015-07-06 14:09 ` Bill Kenworthy
2015-07-08 4:44 ` Jc García
2015-07-08 5:00 ` Anton Shumskyi
2015-07-08 7:00 ` Alan McKinnon
2015-07-08 9:06 ` Florian Gamböck
2015-07-08 9:28 ` Stephan Müller
2015-07-08 10:08 ` Florian Gamböck
2015-07-08 10:13 ` Joerg Schilling
2015-07-08 10:40 ` Florian Gamböck
2015-07-08 10:53 ` Joerg Schilling
2015-07-08 0:48 ` walt
2015-07-08 7:15 ` Florian Gamböck
2015-07-08 13:10 ` Todd Goodman
2015-07-08 13:46 ` Florian Gamböck
2015-07-08 10:17 ` Nikos Chantziaras
2015-07-08 10:29 ` Joerg Schilling
2015-07-09 11:38 ` [gentoo-user] " Stephan Müller
2015-07-09 11:48 ` Neil Bothwick
2015-07-09 12:01 ` Gevisz
2015-07-09 12:07 ` [gentoo-user] " Nikos Chantziaras
2015-07-09 12:20 ` Gevisz
2015-07-09 16:07 ` Neil Bothwick
2015-07-09 17:45 ` Gevisz
2015-07-09 17:54 ` Neil Bothwick
2015-07-09 23:34 ` Nikos Chantziaras
2015-07-09 23:36 ` Nikos Chantziaras
2015-07-09 23:54 ` wraeth
2015-07-10 5:29 ` Franz Fellner
2015-07-10 8:16 ` Neil Bothwick
2015-07-10 15:00 ` Gevisz
2015-07-10 17:39 ` Nikos Chantziaras
2015-07-10 22:18 ` Marc Joliet
2015-07-11 10:22 ` Nikos Chantziaras
2015-07-11 10:39 ` Marc Joliet
2015-07-11 20:56 ` Martin Vaeth
2015-07-12 16:52 ` Nikos Chantziaras
2015-07-12 17:01 ` Neil Bothwick
2015-07-12 22:35 ` Martin Vaeth
2015-07-11 5:53 ` Martin Vaeth
2015-07-11 11:04 ` covici
2015-07-11 20:47 ` Martin Vaeth
2015-07-13 9:21 ` Joerg Schilling
2015-07-13 9:30 ` Peter Humphrey
2015-07-10 6:06 ` Martin Vaeth
2015-07-10 6:18 ` Martin Vaeth
2015-07-10 8:35 ` Neil Bothwick
2015-07-10 15:31 ` Martin Vaeth
2015-07-13 9:39 ` Joerg Schilling
2015-07-13 14:00 ` Martin Vaeth [this message]
2015-07-13 15:03 ` Joerg Schilling
2015-07-13 9:27 ` Joerg Schilling
2015-07-13 13:55 ` Martin Vaeth
2015-07-13 14:40 ` Joerg Schilling
2015-07-09 12:19 ` Nikos Chantziaras
2015-07-09 12:24 ` wraeth
2015-07-09 12:37 ` Nikos Chantziaras
2015-07-09 14:46 ` wraeth
2015-07-10 11:46 ` wraeth
2015-07-11 22:21 ` walt
2015-07-09 12:41 ` walt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='mo0gam$1ps$2@ger.gmane.org' \
--to=martin@mvath.de \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox