On Sunday, October 02, 2011 07:06:36 Michel Fortin wrote:
> On 2011-10-02 05:24:36 +0000, Jonathan M Davis <[email protected]> said:
> > deprecated("message", soft) void func1() {}
> > deprecated("message", hard) void func2() {}
>
> This soft/hard thing is a little obscure, no one will understand what
> it means by looking a it. Why not have separated 'deprecated' and
> 'unavailable' states?
We could just do
deprecated("message");
deprecated("message", full);
"Full" deprecation should be clear enough, I would think. And for simplicity,
you just don't have any argument for partial deprecation.
- Jonathan M Davis
