[Issue 2864] intra-module use of deprecated should be allowed
https://issues.dlang.org/show_bug.cgi?id=2864 Andrei Alexandrescu changed: What|Removed |Added Status|NEW |RESOLVED CC||and...@erdani.com Resolution|--- |WONTFIX --- Comment #5 from Andrei Alexandrescu --- Workaround suggested by @yebblies should be enough. --
[Issue 2864] intra-module use of deprecated should be allowed
http://d.puremagic.com/issues/show_bug.cgi?id=2864 Andrej Mitrovic changed: What|Removed |Added CC||andrej.mitrov...@gmail.com --- Comment #4 from Andrej Mitrovic 2013-02-04 18:12:10 PST --- (In reply to comment #3) > > I think the right fix for that is for the compiler to not complain about > > deprecated symbol usage if the usage is in the same module the deprecated > > symbol is defined in. > > Is this really necessary? It sounds like it could be done using private > symbols and public deprecated symbols. Agreed. And I've heard no complains about this except in this ancient report. -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email --- You are receiving this mail because: ---
[Issue 2864] intra-module use of deprecated should be allowed
http://d.puremagic.com/issues/show_bug.cgi?id=2864 yebblies changed: What|Removed |Added CC||yebbl...@gmail.com Platform|x86 |All Version|2.029 |D2 --- Comment #3 from yebblies 2012-02-15 00:45:34 EST --- (In reply to comment #0) > Andrei Alexandrescu wrote: > > Ok, I've undeprecated rand_seed, sigh. I was hoping I'd eliminate rand() > > entirely from this release, but Walter pointed out it would break too much > > code. So I left rand() and rand_seed() as deprecated. Now I only left > > rand() deprecated so at least the static constructor works. > > I think the right fix for that is for the compiler to not complain about > deprecated symbol usage if the usage is in the same module the deprecated > symbol is defined in. Is this really necessary? It sounds like it could be done using private symbols and public deprecated symbols. -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email --- You are receiving this mail because: ---
[Issue 2864] intra-module use of deprecated should be allowed
http://d.puremagic.com/issues/show_bug.cgi?id=2864 Stewart Gordon changed: What|Removed |Added CC||s...@iname.com --- Comment #2 from Stewart Gordon 2009-08-08 12:17:10 PDT --- The problems are: - even when developing your own library, you'll likely want reminding if you inadvertently use one of your own deprecated entities - when you're ready to release a stable version of your product, you ought to be able to just delete everything that's deprecated and be done with it Perhaps better would be some form of 'deprecatedly public' as I suggested once http://www.digitalmars.com/d/archives/digitalmars/D/Suggestion_More_deprecation_features_73796.html -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email --- You are receiving this mail because: ---
[Issue 2864] intra-module use of deprecated should be allowed
http://d.puremagic.com/issues/show_bug.cgi?id=2864 unkn...@simplemachines.org changed: What|Removed |Added CC||unkn...@simplemachines.org --- Comment #1 from unkn...@simplemachines.org 2009-04-20 22:18 --- It should be left enabled if warnings are requested though, IMHO. I can see deprecating something and wanting to clean my own code of it easily. Would be embarrassing if my own code still used it. -[Unknown] --
