Hi Gunnar,
I should have noted:
On Sat, 2008-11-22 at 12:47 +0800, Tim Post wrote:
> Is the -n switch to echo now considered safe?
As opposed to printf "%s\t" "$foo", which exists in all modern shells
including dash, which is fully POSIX compliant and the default sh
interpreter on many.
Yes, its nit picking :) Also, the LSB app checker (which I love) will
flag warnings if you define your own functions as work-arounds if the
standard LSB init scripts are not present. So something like:
. /lib/lsb/.. || {
foo() {
...
...
}
}
... might be better. While this will raise flags in the app checker, it
guarantees a working script on appliances which are often sparse and not
LSB compliant.
Likewise, telling zsh to emulate sh will also raise a flag. However, we
have no idea what /bin/sh actually points to on a user's machine and we
want the script to work :) If they have an agreeable compiler, it should
'just work' :) While we hope 'sh' is the POSIX compliant invocation of
the shell, its not always the case.
Its better to have one that works everywhere, no?
Cheers,
--Tim
_______________________________________________
Cherokee mailing list
[email protected]
http://lists.octality.com/listinfo/cherokee
