On 6/13/17 5:19 PM, tetsu...@scope-eye.net wrote:
>
> In that case, the answer is simple:
>
> The shell swiftly rejects the script, and provides a clear reason why
> it cannot be run. ("bash: Script requires the en_US.utf8 locale which
> is not installed on this system. Sorry, dude.")
The shell has no business doing this. If a script requires a certain
locale, and won't run correctly without it, the author can ensure that
an assignment to LC_CTYPE produces the desired results.
> This is also why I think this should be an optional "encoding marker"
> at a fairly fixed location in the file, rather than an option setting
> that could occur anywhere in the script: It allows an incompatible
> script to be immediately identified and rejected before it does
> anything.
This is relatively trivial to do with a shell function.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU c...@case.edu http://cnswww.cns.cwru.edu/~chet/
