Issue #6449 has been updated by shyouhei (Shyouhei Urabe).


PS if you need something, tell us _why_ you need something.
In this case we prohibit (re)defining allocator beacuse we
believe redefining new should suffice all needs. If you
don't think so, please show the reason.
----------------------------------------
Bug #6449: new does not call allocate, as advertized
https://bugs.ruby-lang.org/issues/6449#change-26708

Author: schnittchen (Thomas Stratmann)
Status: Rejected
Priority: Low
Assignee: 
Category: 
Target version: 
ruby -v: ruby 1.9.3p217 (2012-05-18 revision 35702) [x86_64-darwin10.8.0]


ruby 1.9.3p217 (2012-05-18 revision 35702) [x86_64-darwin10.8.0] (1.8 seems the same)

class C
  def self.allocate
    Kernel.exit(1)
  end
end

C.new # => <C:...

C.allocate # terminates process

Expected C.new call to invoke allocate, see here: https://github.com/ruby/ruby/blob/trunk/object.c#L1697


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