Summary: | Should writeObject/readObject be a compiler warning? | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Christian Ullenboom <C.Ullenboom> |
Component: | Core | Assignee: | Philipe Mulet <philippe_mulet> |
Status: | VERIFIED FIXED | QA Contact: | |
Severity: | minor | ||
Priority: | P3 | CC: | jverhaeg, rafial |
Version: | 2.1 | ||
Target Milestone: | 2.1 RC1 | ||
Hardware: | PC | ||
OS: | Windows 2000 | ||
Whiteboard: |
Description
Christian Ullenboom
2003-02-10 17:03:17 EST
What do you mean exactly ? If you set "Preferences > Compiler > Unused private types, methodes of fields" from Ignore to Warning it will complain about "unused private..." as said. But if you are working with serialization you will often write private methods readObject(), writeObject(), and this is completely ok and should IMHO not declarate as a waring. But I think this is a view of perception, thus this is a question, not an error. I see. Indeed, we should not flag these, as they are reserved methods. Along this line, we don't report unused private 0-args constructors, as it is a known pattern for blocking instantiation. Special cased these, may want to open this in the future. Fixed in latest *** Bug 31917 has been marked as a duplicate of this bug. *** *** Bug 32164 has been marked as a duplicate of this bug. *** Verified. |