Summary: | Eclipse compiler option: Unused parameters (i.e. never read) | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Chris Grindstaff <chrisg> |
Component: | Core | Assignee: | Philipe Mulet <philippe_mulet> |
Status: | VERIFIED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | CC: | flyguy, martinae, max |
Version: | 2.0.2 | ||
Target Milestone: | 2.1 RC1 | ||
Hardware: | Other | ||
OS: | other | ||
Whiteboard: |
Description
Chris Grindstaff
2002-10-22 12:48:50 EDT
Nice to have. Post 2.1 Resurrecting for investigation, as per request for RC1. *** Bug 28319 has been marked as a duplicate of this bug. *** *** Bug 31243 has been marked as a duplicate of this bug. *** *** Bug 28139 has been marked as a duplicate of this bug. *** Unused parameter diagnosis will now ignore parameters in an abstract method, a main method, an implementation of an abstract method or a method overriding a concrete one. Additional settings got added for enabling the diagnosis of the latter two scenarii. * COMPILER / Reporting Unused Parameter if Implementing Abstract Method * When enabled, the compiler will signal unused parameters in abstract method implementations. * The severity of the problem is controlled with option "org.eclipse.jdt.core.compiler.problem.unusedParameter". * - option id: "org.eclipse.jdt.core.compiler.problem.unusedParameterWhenImplementi ngAbstract" * - possible values: { "enabled", "disabled" } * - default: "disabled" * * COMPILER / Reporting Unused Parameter if Overriding Concrete Method * When enabled, the compiler will signal unused parameters in methods overriding concrete ones. * The severity of the problem is controlled with option "org.eclipse.jdt.core.compiler.problem.unusedParameter". * - option id: "org.eclipse.jdt.core.compiler.problem.unusedParameterWhenOverriding Concrete" * - possible values: { "enabled", "disabled" } * - default: "disabled" Fixed Verified. |