Comment #3 by bearophile_hugs — 2013-03-12T17:42:21Z
Andrej Mitrovic:
>I thought bearophile just wanted the ability to highlight the function in some way to make it stand-out more.<
I wanted dmd to add <del></del> around the function, to make it stand-oud less than other functions (to make it more visually clear they are deprecated).
Walter:
>Yes, it should wrap the whole thing. Then bearophile can add his own definition of DEP to highlight as he wishes with it.<
This issue asks for <del></del> in the standard online documentation. I don't have personal uses for such a macro.
Comment #4 by bearophile_hugs — 2013-03-12T17:48:06Z
Walter:
>the default expansion for deprecated symbols should be to nothing. Otherwise, people will continue to use them.<
I think this isn't a good idea. If I am using a function in my code and it's deprecated this forces me to go read the source code.
If you don't want a function to be visible in the documentation then replace its /**...*/ and /// with /*...*/ and //.
In Scala deprecated names are clearly visible as deprecated, but they aren't invisible, I think this is the right default:
http://twitter.github.com/algebird/com/twitter/algebird/BloomFilterMonoid.html
Comment #5 by andrej.mitrovich — 2013-03-12T17:49:58Z
(In reply to comment #3)
> This issue asks for <del></del> in the standard online documentation. I don't
> have personal uses for such a macro.
Right, but you can't add <del></del> without knowing where to inject it to, hence why you need a macro first. Then for HTML generation $(DEPRECATED foo) will simply expand to <del>foo</del>.
So essentially these are two feature requests, one depends on the other.
Comment #6 by andrej.mitrovich — 2013-03-12T17:51:28Z
(In reply to comment #5)
> So essentially these are two feature requests, one depends on the other.
Although perhaps I should have opened a separate issue instead of hijacking your ER. Sorry about that!
Comment #7 by bearophile_hugs — 2013-03-12T18:36:14Z
(In reply to comment #5)
> Right, but you can't add <del></del> without knowing where to inject it to,
> hence why you need a macro first.
I am aware of this.
(In reply to comment #6)
> Although perhaps I should have opened a separate issue instead of hijacking
> your ER. Sorry about that!
Don't worry, small misunderstandings between persons are common. And I think the two issues are closely related.