Improving deprecation management

[Jeremy Powers]

On Wed, Nov 13, 2013 at 11:13 AM, Dicebot <public at dicebot.lv> wrote:

> What about connecting it to date of ....
>

Using a date is the wrong approach for deprecation.  When you are
deprecating something, you are stating that in a future release it will no
longer work - it just happens that releases usually arrive at a point in
time.  Tying it to a date implies every user will pick up the new version
exactly when it is released... which only happens when you have zero users.

If you want stuff depending on deprecated functionality to break at a
certain point, you should approach it from a version management standpoint.
 With the existing deprecation annotation, you can tag with versions to
help.  Your step #2 should be 'removal version' rather than 'removal date'
- and then perhaps tie in with dependency management versions or some such.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.puremagic.com/pipermail/digitalmars-d/attachments/20131113/2c3a292e/attachment.html>