Re: ash or bash not good /bin/sh replacements?
Herbert Xu <email@example.com> writes:
> In article <19980528121257.A3590@molec3.dfis.ull.es> you wrote:
> > Is it a bug in ash or in bash?
> Neither. POSIX doesn't say that the dot command can take on any arguments. So
> the correct thing to do is to set $1 $2 etc. with set before you use the dot
> command. I've tested it and it works with both ash and bash.
Or you can use the shorthand notation:
set -- arg1 arg2 ...
I would like to see an option to bash to print warnings for any non-posix
extensions. There are too many of these cases cropping up.
To UNSUBSCRIBE, email to firstname.lastname@example.org
with a subject of "unsubscribe". Trouble? Contact email@example.com