Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #15707 > unrolled thread
| Started by | Martijn Dekker <martijn@inlv.org> |
|---|---|
| First post | 2019-12-08 10:55 +0100 |
| Last post | 2019-12-08 10:55 +0100 |
| Articles | 1 — 1 participant |
Back to article view | Back to gnu.bash.bug
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: [PATCH] allow process substitution in POSIX mode Martijn Dekker <martijn@inlv.org> - 2019-12-08 10:55 +0100
| From | Martijn Dekker <martijn@inlv.org> |
|---|---|
| Date | 2019-12-08 10:55 +0100 |
| Subject | Re: [PATCH] allow process substitution in POSIX mode |
| Message-ID | <mailman.514.1575798924.1979.bug-bash@gnu.org> |
Op 08-12-19 om 10:29 schreef Oğuz: > I think otherwise. In POSIX mode Bash should at least print warnings > about features POSIX lets implementations provide but doesn't mandate, > like function, select, [[, etc. That would be a far bigger change than just allowing process substitution. Also, there is already a good shell that does this: yash <http://yash.osdn.jp/>. Its POSIX mode is deliberately strict and restrictive and does not allow any non-portable functionality, so it's a really good compatibility testing tool. Then there are also shells that simply don't implement much more than POSIX, such as dash. They're useful for that as well. So I don't think bash needs to fulfill that function. Bash's POSIX mode has always been simply a way to run POSIX scripts, with or without mixing them with bash scripts. - M. -- modernish -- harness the shell https://github.com/modernish/modernish
Back to top | Article view | gnu.bash.bug
csiph-web