On 5 Oct 2014 08:10, "Daniel Murphy via Digitalmars-d" < [email protected]> wrote: > > "David Nadlinger" wrote in message news:[email protected]... > > >> Second, if I'm using "-w", I'm typically interested in errors if I write fishy code, not because some third-party library I just updated made a small change to its API. I don't see where the advantage would be in conflating the two things. > > > You don't get 'warning' deprecations from third-party code, you get them from the compiler when you use a feature that is on its way to being deprecated. Usually because it's fishy.
The 'deprecated' for all intents and purposes might as well emit a warning when you try to use deprecated features of third party code. Didn't you Phobos devs have a hardDeprecation message too that would force an error?
