On 27/01/2021 12.57, Koichi Murase wrote:
> There was already a discussion to use ${ command } for no-fork command
> substitutions as ksh does.
I would find that syntax very confusing, as ${var} is used to access
variables, so then only the starting space (and the ending semicolon)
would distinguish this as a command instead of a variable.
> In ksh, ${( ... )} is a valid construct of this kind (though it seems
> equivalent to $(...)), so your suggestion actually conflicts with this
> possible future syntax.
Anything using ( ) would suggest something involving a subshell. Maybe
$[{ ... }] or even ${{ ... }} would be clearer?
Peter
