Hi,

In message "Re: Change in system() behaviour"
    on Tue, 20 Nov 2007 04:07:55 +0900, Dave Thomas <dave / pragprog.com> writes:

|In 1.8,  system("badcmd")  returned false.
|In 1.9, it raises Errno::ENOENT
|
|Is this an intended change?

Yes.  The command execution has tree states:

  * command execution failed (non zero exit status)
  * command execution succeeded (zero exit status)
  * command not found

The new "system" gives true/false/exception respectively.  We thought
these three should be distinguished.  Returning nil for "not found"
in [ruby-core:13715] might be an idea.

							matz.