News for hackers. Stuff that matters.
Re:Filenames and Pathnames in Shell: How to Do It Correctly by drbaba on Tuesday June 20, 2023 @02:41AM (#36400512)
> well, except for the fact that MacOS defaults to zsh now.

But Zsh is also POSIX sh compatible, is it not?

Re:Filenames and Pathnames in Shell: How to Do It Correctly by meinheld111 on Tuesday June 20, 2023 @03:50AM (#36400925)
No.

Afaik it can be thou

Re:Filenames and Pathnames in Shell: How to Do It Correctly by distcs on Tuesday June 20, 2023 @06:26AM (#36401996)
Zsh is not POSIX compatible. You need to enable many flags to make it POSIX compatible.

Zsh:

  $ A="foo bar baz"; for X in $A; do echo $X; done 
  foo bar baz
Dash:

  $ A="foo bar baz"; for X in $A; do echo $X; done 
  foo
  bar
  baz
Re:Filenames and Pathnames in Shell: How to Do It Correctly by Calzifer on Tuesday June 20, 2023 @06:55AM (#36402222)
> You need to enable many flags to make it POSIX compatible.

or use 'emulate sh' to enable many flags at once.

(and I personally would prefer if other shells would behave like Zsh and not word split unquoted variables by default)

Re:Filenames and Pathnames in Shell: How to Do It Correctly by JdeBP on Tuesday June 20, 2023 @07:28AM (#36402510)
This is true for the Bourne Again, Watanabe, and Korn shells too. The default mode is not the POSIX-conformant mode, but is the shell's native mode. This does not, however, make these shells "not POSIX compatible" any more than it makes the Z shell "not POSIX compatible". In all of them, one has to do non-default stuff, from setting particular environment variables through invoking the shell with a particular name to adding extra command-line options, to pick the POSIX-conformant mode.
Re:Filenames and Pathnames in Shell: How to Do It Correctly by JdeBP on Tuesday June 20, 2023 @07:15AM (#36402395)
The Z, Korn, Debian Almquist, Watanabe, and Bourne Again shells are all capable of running POSIX-conformant scripts. So if one has a POSIX-conformant shell script, one can use the Z shell to run it, yes.

The major factors when it comes to portability are, for all of them, that (a) the POSIX-conformant mode has to be specially invoked, and (b) even if invoked in conformance mode the non-POSIX parts are not always turned off. It's not that the shells won't handle POSIX-conformant scripts. They even mostly will in their (default) non-conformant modes. It's rather that it's difficult to discipline onesself to keep within the bounds of POSIX conformance when writing, even if one tests with conformance mode switched on.

The Debian Almquist and Watanabe shells are the best at preventing non-POSIX stuff creeping in by accident, because the former doesn't have much of it in the first place and the latter actually does things like turn off non-POSIX option arguments and builtins so that they generate errors in conformance mode and one can detect accidental "Yashisms" in testing. With the others, it's easier to accidentally use some of their various extensions and not spot it without explicitly testing with something in addition to the shell in its POSIX-conformant mode.