On Tue, Aug 12, 2008 at 02:14:07PM +0200, Allison Randal wrote: > Will Coleda wrote: >> I agree that any removed feature should have a deprecation cycle; >> Here's my pitch for how we've already done that; the list of >> deprecated features has RTs; the RT listed what was going to have to >> happen for some time now; This covers us on the deprecation >> notification.
I'm totally willing to go along with this pitch; I'm just thinking that someone watching DEPRECATED.pod would never have guessed that removing C<getclass> (the note for this ticket) would also cause C<sin>, C<exp>, C<log>, etc. to disappear as well. :-) > Let's do a quick query of other languages: Is anyone else affected by > the change? And, is a quick update to a method call instead of the > builtin a workable solution for you? > > Overall, I suspect updating any affected languages is less hassle than > backing out the patch (that is, I don't expect wide usage), so it's the > better path forward. +1. And Coke++ for having done the work to make this patch. Pm
