| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Re: why George puts his foot in his mouth |
From: vwheeler
> If we mark superseded classes, methods, and fields clearly and
> unambiguously as "deprecated", the programmers will know where to
> concentrate their attention. Also, the compiler will be able to help
> with this process, by bringing unintentional uses of deprecated APIs
> to the programmer's attention.
The {at}deprecated is a comment to the programmer(s) what better place to put
it then in the comments.
Rich wrote:
> You should. From
> http://java.sun.com/j2se/1.3/docs/guide/misc/deprecation/deprecated.html.
>
>
>
> As far as the compiler is concerned, the presence of the string
> "{at}deprecated" at the beginning of a documentation comment line
> (except for whitespace) causes it to place a "Deprecated" attribute
> in the output classfile for the corresponding class, field, or
> method.
>
>
> and
>
>
> Still, the compiler has heretofore ignored and should generally
> ignore documentation comments. This is an admittedly irregular
> exception to that practice. But the other design options for
> deprecation involve worse sorts of irregularity.
>
> Rich
>
>
> "Adam Flinton" * Origin: Barktopia BBS Site http://HarborWebs.com:8081 (1:379/45)SEEN-BY: 633/267 270 @PATH: 379/45 1 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.