Issue #5728 has been reported by Akira Tanaka.

----------------------------------------
Bug #5728: SystemExit.new(bool, message)
http://redmine.ruby-lang.org/issues/5728

Author: Akira Tanaka
Status: Open
Priority: Normal
Assignee: 
Category: 
Target version: 
ruby -v: ruby 2.0.0dev (2011-12-08 trunk 33981) [x86_64-linux]


I found SystemExit.new doesn't take a bool as exit status:

It works well if an integer is given for status.

  % ./ruby -e 'SystemExit.new(0, "msg")' 
  % ./ruby -e 'SystemExit.new(1, "msg")'  

But it doesn't work if the status is a bool.

  % ./ruby -e 'SystemExit.new(true, "msg")'
  -e:1:in `initialize': wrong number of arguments (2 for 0..1) (ArgumentError)
	  from -e:1:in `initialize'
	  from -e:1:in `new'
	  from -e:1:in `<main>'
  % ./ruby -e 'SystemExit.new(false, "msg")'
  -e:1:in `initialize': wrong number of arguments (2 for 0..1) (ArgumentError)
	  from -e:1:in `initialize'
	  from -e:1:in `new'
	  from -e:1:in `<main>'

  % ./ruby -v
  ruby 2.0.0dev (2011-12-08 trunk 33981) [x86_64-linux]

I think SystemExit.new should accept a bool.




-- 
http://redmine.ruby-lang.org