Front page | perl.perl5.porters |
Postings from February 2009
On Thu, Feb 19, 2009 at 04:33:09PM +0100, Steffen Mueller wrote: > > On an aside: I totally agree with you and others that adding mandatory > warnings to existing non-buggy modules that can't currently be removed > from core is a spectacularly bad idea. I'd go one step further. I'd say any warning that is nothing more than "today we no longer like this module; we're putting warnings into it so you do the easy thing of no longer using warnings (it proven to not be very useful), or do the hard thing and change your code to use the module-du-jour (which we might bug you about next week)", is a really bad idea. Except for the person lobbying for the new module, who's going to benefit from such a warning? Warnings should be there to warn the user that perl might do something else than the user intended. I don't think that's the case with File::Find. AbigailThread Previous | Thread Next