Summary: | [compiler] Detect and visually indicate auto-boxing in Jdk1.5 code | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | BenH <ben_hutchison> |
Component: | Core | Assignee: | Philipe Mulet <philippe_mulet> |
Status: | VERIFIED FIXED | QA Contact: | |
Severity: | enhancement | ||
Priority: | P3 | CC: | eclipse, eclipse |
Version: | 3.1 | ||
Target Milestone: | 3.1 M5 | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: |
Description
BenH
2004-11-08 17:46:12 EST
This is something we had in mind, like we do optionally warn when performing innerclass access emulation. Another one would be to warn when inserting generic cast (implicitly during compile). *** Bug 80457 has been marked as a duplicate of this bug. *** *** Bug 68269 has been marked as a duplicate of this bug. *** Added optional compiler diagnosis when boxing/unboxing conversion is performed. Corresponding problem IDs are: IProblem.BoxingConversion and IProblem.UnboxingConversion. * COMPILER / Reporting Boxing/Unboxing Conversion * When enabled, the compiler will issue an error or a warning whenever a boxing or an unboxing * conversion is performed. * - option id: "org.eclipse.jdt.core.compiler.problem.autoboxing" * - possible values: { "error", "warning", "ignore" } * - default: "ignore" Fixed Verified in I20050214 |