From: David MacMahon <davidm@...>
Date: 2013-06-04T13:39:11+09:00
Subject: [ruby-core:55288] Re: [ruby-changes:28951] zzak:r41003 (trunk): * process.c: Improve Process::exec documentation


On Jun 3, 2013, at 7:07 PM, Zachary Scott wrote:

> The original wording was:
> 
> - *  The standard shell means always <code>"/bin/sh"</code> on
> Unix-like systems,
> - *  <code>ENV["RUBYSHELL"]</code> or <code>ENV["COMSPEC"]</code> on
> Windows NT series, and
> - *  similar.
> 
> I've only modified the grammar "means always" to "always means", right?

No, you also added "same as" before ``ENV["RUBYSHELL"]'' and put parentheses around the ``or ENV["COMSPEC"] on Windows'' clause.

With these additional changes it could easily be interpreted to mean that the ``same as ENV["RUBYSHELL"]'' clause applies to Unix-like systems (i.e. that ENV["RUBYSHELL"] == '/bin/sh' on Unix systems) and that only the ``or ENV["COMSPEC"] on Windows'' clause applies to Windows.

Here's the new wording that @akr was concerned about:

+ *  The standard shell always means <code>"/bin/sh"</code> on Unix-like systems,
+ *  same as <code>ENV["RUBYSHELL"]</code>
+ *  (or <code>ENV["COMSPEC"]</code> on Windows NT series), and similar.

Dave