trans wrote:
> Besides the issues you mention (new API and adoption), I see other
> reasons something like this isn't going to make much headway.
> 
> 1. You can use -w ruby option to get warnings about methods that are
> redefined.
> 
> 2. Raising an error on a method redefinition is too much. There are
> times when that's what you need to do, say to temporary patch a bug.

Really? Raising an error is too much? Consider that if you get this 
warning, what it really means is that you just clobbered someone else's 
method and their code will most definitely fail because of this. If this 
isn't the time for "fail fast" then I don't know what is. Clobbering a 
method (for example to patch a bug) should be the exception case; then 
you could easily undef the method before defining your patched version.

Daniel