2017-07-26 07:49:46 +0700, Robert Elz: [...] > Personally I remain somewhat on the fence in this whole issue, apart > from not wanting to require that the shell be able to "exec func", or > "exec built-in" I don't currently really have an opinion on any of this. > That is, I don't object to shells that allow that, nor to shells that > want to build-in env, and allow env to run other built-ins or functions > (that one I think more useful than exec of a built-in) but I would not > want to require that either. And of course, any script that relies upon, > or even uses, any of the "unusual" variants of any of this is horribly > non-portable. [...]
To what (real, not theoretical) system/shell is: env LC_ALL=C printf "%.2g\n" 3.14159 to call the non-builtin "printf" non-portable? -- Stephane