Front page | perl.perl5.porters |
Postings from January 2012
* David Golden <xdaveg@gmail.com> [2012-01-29T21:21:07] > Right now, perlpolicy defines "deprecated" and says that deprecated > features will warn. I wonder if it would be better to introduce a new > category, "scheduled for deprecation", which would be public notice of > future deprecation for one stable release cycle, after which the > feature would be "deprecated" (and begin warning), after which the > feature would be "removed". This three-stage removal process would > give an extra period of notice before code behavior changes. (I still > expect few to pay attention until code warns, but at least we'd be > able to tell them they had notice*.) Please let me know whether I understand properly. Here is an example based on my understanding of your suggestion. Please note that, for the sake of simplicity, I have not included feature.pm behavior in this example. 1. We realize that adding foozles was a horrible mistake. 2. We add "foozles" to the Future Deprecations section of perl5200delta Now, come the release of 5.20, everyone reading the placard knows that foozles are slated for demolition. 3. In 5.21.0, we add the deprecation warning. Now, when 5.22 lands, the code of those unfortunate souls who used foozles begins issuing warnings at some yet-to-be-decided frequency. 4. In 5.23.0, we remove foozles. The code that warned in 5.22 is now fatal to compile or run. -- rjbsThread Previous | Thread Next