On 4/24/2018 11:55 AM, Stephan Herrmann wrote:
On 03.04.2018 02:49, Alex Buckley wrote:
You're right -- the JLS does not mandate a warning when compiling code
on the classpath that uses code in deprecated modules.
Wouldn't it be more consistent to give such warnings?
Why should writing code in
Thanks, Alex, for your answer, and sorry for the long delay on my side.
I found the background regarding deprecation of packages quite interesting,
and agree to most of what you say.
On 03.04.2018 02:49, Alex Buckley wrote:
You're right -- the JLS does not mandate a warning when compiling code
On 4/1/2018 4:31 AM, Stephan Herrmann wrote:
Packages: JLS & javadoc agree that @Deprecated applied to a package
has no effect. Given that @Target explicitly includes PACKAGE this
looks inconsistent to me. A user adding @Deprecated to a package would
certainly expect *some* effect, no?
I unders
I'm looking at how deprecation affects elements larger than types,
and it seems to me that deprecation is much weaker than it could be.
Packages: JLS & javadoc agree that @Deprecated applied to a package
has no effect. Given that @Target explicitly includes PACKAGE this
looks inconsistent to me.
