On Saturday, 17 November 2012 at 17:42:03 UTC, Alex Rønne Petersen wrote:
> And that's the entire problem.
>
> People shouldn't have to go in and change anything to make code build just because something has been deprecated.

It's just an alternative compilation mode.
And may be people shouldn't go in and enter admin password to install software?


On Saturday, 17 November 2012 at 18:48:11 UTC, Jonathan M Davis wrote:
> Also, if
> you start compiling with -d, then you have no idea what is and isn't
> deprecated, and then you're that much more screwed when a deprecated symbol is
> actually removed.

You compile with -d because previously the build broke, so you know you use deprecated features.

On Sunday, November 18, 2012 11:00:09 Kagamin wrote:
> You compile with -d because previously the build broke, so you know you use deprecated features.

Except that then you forget about it and never get around to updating your code so that it doesn't use the deprecated features, and when they're removed, your code breaks. -d is arguably a rather evil flag actually, and there are some of us would wouldn't mind having it gone entirely.

With deprecated warning, then code doesn't break immediately, and the programmer gets reminded that they need to update their code. It's just plain a better model.

- Jonathan M Davis