From: mathew Date: 2010-11-27T08:58:24+09:00 Subject: [ruby-core:33410] Re: [Ruby 1.9-Feature#2351] system() hardlinked to /bin/sh --0016363b870e5696ee0495fd7fb8 Content-Type: text/plain; charset=ISO-8859-1 On Fri, Nov 26, 2010 at 08:18, Motohiro KOSAKI wrote: > And if we accept this proposal, system() will lose user enviroment > portability. e.g. csh has completely different syntax from /bin/sh. Thus, > distributed ruby scripts will not be able to use system(). > Surely anyone using system() to execute a shell script will be using a shebang (#!) line to specify the shell the script is supposed to be executed by? If you don't, you're likely to discover that ksh is the standard POSIX shell, not sh; and then there's the whole issue of bash vs ash vs sh. mathew --0016363b870e5696ee0495fd7fb8 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Fri, Nov 26, 2010 at 08:18, Motohiro KOSAKI <redmine@ruby-lang.org> wro= te:
And if we accept this proposal, system() will lose user e= nviroment portability. e.g. csh has completely different syntax from /bin/s= h. Thus, distributed ruby scripts will not be able to use system().

Surely anyone using system() to execute a = shell script will be using a shebang (#!) line to specify the shell the scr= ipt is supposed to be executed by?

If you don'= t, you're likely to discover that ksh is the standard POSIX shell, not = sh; and then there's the whole issue of bash vs ash vs sh.


mathew
--0016363b870e5696ee0495fd7fb8--