Summary: | [compiler] Should the compiler report deprecation from within the same compilation unit ? | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Olivier Thomann <Olivier_Thomann> |
Component: | Core | Assignee: | Srikanth Sankaran <srikanth_sankaran> |
Status: | VERIFIED WONTFIX | QA Contact: | |
Severity: | minor | ||
Priority: | P3 | CC: | amj87.iitr |
Version: | 3.7 | ||
Target Milestone: | 3.7 M7 | ||
Hardware: | PC | ||
OS: | Windows 7 | ||
Whiteboard: |
Description
Olivier Thomann
2011-01-21 14:08:12 EST
Srikanth, please let me know what you think. (In reply to comment #1) > Srikanth, please let me know what you think. Unless there is strong sentiment otherwise, I am inclined to leave the current behavior as it is. When the compilation units are different, the potential for provenance of the the client code and service providing code differing is there and as such the warning is useful to communicate intent and avoid "out of sight out of mind" situations. When things are in the same compilation unit, the authorship/ownership is the same and fixing the uses of about to deprecated code can be taken atomically with the act of deprecation itself. Closing as WONT_FIX. Verified for 3.7M7 |