a small study of "deprecate"

[Rob T]

On Wednesday, 7 November 2012 at 14:05:06 UTC, deadalnix wrote:
> Here is how I see it (and all language fail at that as far as 
> my knowledge goes).
>
> Deprecation comes with a date and a message.
>
> Before the date, the dev is presented with the deprecation 
> message when compiling. The message explain why the function is 
> deprecated and what to use instead.
>
> After the date, the message pops, but now it is an error 
> (unless some flag is used).
>
> At some point the function may be removed.

The message should refer the reader to a resource url for more 
details on the specific depreciation.

--rt