Community
Participate
Working Groups
Code based, org.eclipse.jdt.internal.compiler.ast.ASTNode 1.56 The isFieldUseDeprecated, isMethodUseDeprecated and isTypeUseDeprecated were initially meant to provide information about deprecation only. Deprecation and access restriction being similar in many respects, it made sense to combine checks for those two aspects, and those methods now carry the additional responsibility of access restrictions checks. We are somewhat only at the half of the journey though, since the method names are no more reflecting what is done, on the one hand, and deprecation and access restrictions checks leave the responsibility to raise errors to different parties (the caller for the former, the implementor for the latter). The situation calls for some refactoring. Philippe's advice is to consider what is done about cast checks.
Frédéric, do you want me to give it a try, or should I reassign this bug to you?
Ooops... Frédéric rightly remarks that this is not in his scope. Start over... Philippe, do you want me to give it a try, or should I reassign this bug to you?
