We do have this feature. There is a function Parrot_warn_deprecated that we call and will print out warnings if you're using a deprecated feature. There are performance implications for this, especially if we are calling a deprecated function many times (only in debug mode, I think), and not all renameable functions use this because it would basically have to go everywhere. For something like TT #443 this is way overkill, but the idea exists and is used in other deprecations.
--Andrew Whitworth On Wed, Dec 1, 2010 at 3:20 AM, Lucian Branescu <[email protected]> wrote: > On Wednesday, 1 December 2010 at 00:34, Jonathan Leto wrote: > > Howdy, > > Whiteknight++ asks some good questions that we need to seriously think > about. > > I think a utility that reads HLL source code and then prints out a > list of deprecations > with links to deprecation pages would mostly solve this problem. I am > willing to help > hack on this. > > We may also want to look into making something like > Package::DeprecationManager [0] > for Parrot. > > Deprecations will always happen. We need to make it as easy as > possible for HLL devs > to understand and respond to them. > > Python 2.6+ issues warnings at runtime if you use something deprecated in > Python 3 (or even Python 2.7 sometimes). Something like that would be > awesome. _______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
