From: "mame (Yusuke Endoh)" <mame@...>
Date: 2012-03-28T00:49:29+09:00
Subject: [ruby-core:43760] [ruby-trunk - Feature #5673][Assigned] undef_method probably doesn't need to raise an error


Issue #5673 has been updated by mame (Yusuke Endoh).

Status changed from Open to Assigned
Assignee set to matz (Yukihiro Matsumoto)
Target version changed from 1.9.4 to 2.0.0


----------------------------------------
Feature #5673: undef_method probably doesn't need to raise an error
https://bugs.ruby-lang.org/issues/5673#change-25270

Author: trans (Thomas Sawyer)
Status: Assigned
Priority: Normal
Assignee: matz (Yukihiro Matsumoto)
Category: 
Target version: 2.0.0


Is there any significant reason for #undef_method to raise an error if the method is already undefined? If no, then change it to just continue on. It can return true/false to relay if was undefined vs already undefined.



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