From: "matz (Yukihiro Matsumoto)" <matz@...>
Date: 2012-04-01T01:30:17+09:00
Subject: [ruby-core:44011] [ruby-trunk - Feature #5673][Feedback] undef_method probably doesn't need to raise an error


Issue #5673 has been updated by matz (Yukihiro Matsumoto).

Status changed from Assigned to Feedback

I think raising error can catch potential bugs earlier.  What is the benefit of ignoring error?

Matz.

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

Author: trans (Thomas Sawyer)
Status: Feedback
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/