Christopher Albert wrote:
> Phillip,
>
> Tom agrees with you, and now I do to. I'll change it to a TERM signal in the next
> version.
> While the $() syntax is equivalent to backticks in recent Bash (and I prefer it
> for readability,
> and also becaue the backtick is in a confusing place on my french azerty
> keyboard...), I think
> Tom and Toby are right that it might be better to use backticks for portability.
> I'll change this too.
> I'll post a new version soon before I send it to the jboss-dev list.
My preferred option would be to keep the $(...) syntax and change the
shell it uses to ksh. I depends how portable you want it. I don't know
of a UNIX or UNIX-like system that doesn't have ksh. ksh is preferable
to sh for scripting in almost every way (see the recent /. interview
with Mr Korn).
Of course, the problem with this is that then you need to change the
filename from .sh to .ksh so as not to mislead people. A solution to
this is to leave off the .sh altogther. A better solution is to treat
the .sh or .ksh as a source file and "compile" it to a file without the
.sh or .ksh. This compilation step can then fill in the appropriate path
to the desired shell on the target system for the #! bit at the top.
Or you could just use sh.
Toby.
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
List Help?: [EMAIL PROTECTED]
