On 01/06/2012 17:33, David Korn wrote:
What I could do is modify the test and [...] utilities to display
an error for every undefined case. However, I suspect that if I
do this, I will break some script that allowed this combination in
some version of test.
It isn't even clear what message should be given. It the problem
that foo is not a operator, or is the problem that there is an
extra argument?
One of the problems with shell programming is that it leans heavily
on the user to *know* which features are portable/standard in the
shell of their choice.
It would be nice to have some way of setting an option in the shell for
testing *strict* conformance to posix. (like set -o strict).
bash already has 'set -o posix', but I think this allows certain
features to slip through.
Henk
_______________________________________________
ast-users mailing list
[email protected]
https://mailman.research.att.com/mailman/listinfo/ast-users
