[ ruby-Bugs-4498 ] raise can create custom exception objects which aren't properly initialized

Bugs item #4498, was opened at 2006-05-17 11:36
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=1698&aid=4498&group_id=426

Category: Core
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Sylvain Joyeux (lapinot)
Assigned to: Nobody (None)
Summary: raise can create custom exception objects which aren't properly initialized

Initial Comment:
If one defines a custom exception type with a initialize() that needs argument:

class MyError < RuntimeError
  def initalize(info)
    @info = info
  end
end



then Ruby allows to raise an exception *without creating the object yourself*
  raise MyError, "this is an error message"

which is obviously wrong, since the MyError object created by raise won't be properly initialized. IMO, the explicit call to ::new should be the rule here, i.e.
  raise MyError.new(info), "this is an error message"

In fact, I'd expect 
  raise klass, message
to behave as
  raise klass.new, message
which is not the case

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=1698&aid=4498&group_id=426