From: Alexey Muranov <muranov@...>
Date: 2011-11-26T18:47:38+09:00
Subject: [ruby-core:41304] [ruby-trunk - Feature #5673] undef_method probably doesn't need to raise an error


Issue #5673 has been updated by Alexey Muranov.


I can imagine that raising errors in such cases might be meant to discourage excessive metaprogramming.
----------------------------------------
Feature #5673: undef_method probably doesn't need to raise an error
http://redmine.ruby-lang.org/issues/5673

Author: Thomas Sawyer
Status: Open
Priority: Normal
Assignee: 
Category: 
Target version: 1.9.4


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://redmine.ruby-lang.org