On Sun, 06 Aug 2000, Johan Vromans wrote:
> Perl6 RFC Librarian <[EMAIL PROTECTED]> writes:
>
> > There are times when one may need (or desire) to change the shell used
> > for interpretation, as well as force shell interpretation, regardless
> > of optimization, for consitency's sake.
>
> print `fancysh -c 'your uninterpreted and unoptiomized shell command'`;
>
> Or am I overlooking something?
Well, for me, the lazyness factor. :-)
There is the potential (for someone, I'm sure, as I haven't yet) to
want to run all system commands through an alternate command
interpreter - including the ones you didn't write. Me, I just want to
run most of them in a couple of applications.
@results = shell_me($shell_command);
# With the appropriate sub backing it up
is, to me, the entire point behind the backticks.
@results = `$shell_command`;
It's intuitive, quick, and DWIM.
Surely, Perl on Windows doesn't require /bin/sh, does it?
--
Bryan C. Warnock
([EMAIL PROTECTED])
