http://d.puremagic.com/issues/show_bug.cgi?id=9960
--- Comment #3 from Don <[email protected]> 2013-04-22 01:29:25 PDT --- > In fact, a different template might get picked with "-de" compared to the default "-dw" so we shouldn't ever gag deprecation errors during template instantiation, no matter whether "-v" was specified or not. This is incorrect, it would remove the possibility of compiling without deprecated features, which is the most important and common case! This would break existing code, and worse, would give no way to fix it. It's actually a difficult problem. What's needed instead, I think, is a flag for "tell me which recently deprecated features I'm still using." Suppose feature F7 is deprecated in release 7, and feature F9 is deprecated in release 9. Initially your code contains F7 and F9. When release 7 is released, you fix your code so that it no longer uses F7. Once you've done this, you never want to hear a warning about F7 again, you want to act as if it had never existed in the language. Then, release 9 happens. Now, you want to know when you are using feature F9. You actually don't care about F7 any more. The point is -- you only care about the use of deprecated features *while you are in the process of removing them*. The compiler should be silent except in that case. The only possibility I can see is a compiler to flag to tell the compiler that this is what you're doing. -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email ------- You are receiving this mail because: -------
