That would depend on how they decide to implement it. If they use the same method to warn about all deprecations, changing it to raise would be as simple as overriding that method.
This has been committed now. As you can see from deprecation_test.rb in activesupport, it's fairly easy to monkeypatch. Raising an exception should be easy. For a while we considered raising an exception as a built in measure, however while we want to get your attention, it's probably not good to crash your app repeatedly until you check your exception logs.
One could also change it to email the coder on each deprecated call. The possibilities are endless :P I also like the idea of the code scanner task, even if it's unreliable. It may detect things that are otherwise undetecable, such as the use of @content_for_layout
As Jamis mentioned, we can quite easily catch references to deprecated instance variables. I'll hopefully have something to commit in the next few days which takes care of that. -- Cheers Koz _______________________________________________ Rails-core mailing list Rails-core@lists.rubyonrails.org http://lists.rubyonrails.org/mailman/listinfo/rails-core
