Summary: | [compiler] should not warn about unused field when native method present | ||||||
---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Paulo R. Panhoto <paulo> | ||||
Component: | Core | Assignee: | Srikanth Sankaran <srikanth_sankaran> | ||||
Status: | VERIFIED FIXED | QA Contact: | |||||
Severity: | trivial | ||||||
Priority: | P3 | CC: | daniel_megert, jerome_lanneluc, Olivier_Thomann | ||||
Version: | 3.4 | ||||||
Target Milestone: | 3.6 M5 | ||||||
Hardware: | All | ||||||
OS: | All | ||||||
Whiteboard: | |||||||
Bug Depends on: | |||||||
Bug Blocks: | 360832 | ||||||
Attachments: |
|
Description
Paulo R. Panhoto
2008-08-12 13:43:10 EDT
*** This bug has been marked as a duplicate of bug 55696 *** Actually not a dup. Dani, What is the JDT/UI team's take on the option suggestion below ? Do you want to expose this to the user or have JDT/Core conservatively suppress the warning in the presence of native methods ? -- Thanks. (In reply to comment #0) > which has a variable and a native method. In the presence of a native method, > eclipse has no way to tell whether this variable is being used locally or not. > Still, it issues warning message. There should be an option, at best to set > whether I want or not this warning in the presence of native methods or, at > least, the platform should issue no warning at all for this circumstance. Flagging it as problem is wrong and should be fixed. There's no need for an additional option. Created attachment 155588 [details]
Proposed patch
Released in HEAD for 3.6M5 Verified for 3.6M5 using I20100125-0800 |