Bug 274802 - unnecessary code error: 'Local variable is never read' and 'Unused local or private member'
Summary: unnecessary code error: 'Local variable is never read' and 'Unused local or p...
Status: VERIFIED INVALID
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.5   Edit
Hardware: Macintosh Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: 3.5 RC1   Edit
Assignee: Srikanth Sankaran CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-04 05:49 EDT by Holger Staudacher CLA
Modified: 2009-05-14 11:52 EDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Holger Staudacher CLA 2009-05-04 05:49:40 EDT 
It seems that the default values for the unnecessary code has changed. The default for 'Local variable is never read' and 'Unused local or private member' is now error. This comes to errors when you check out some other Eclipse projects i.e. RAP. This behaviour appears with 3.5M6 and still exist in M7.
Comment 1 Srikanth Sankaran CLA 2009-05-04 06:15:30 EDT 
No, the default values should be "warning" for both
the settings you mention. You can confirm this by
switching to a fresh workspace (File + Switch workspace ...
and type in the name of a non-existent workspace) and
looking for the default values of these settings
there.

What did happen at M6 time was that the compiler started
issuing warnings in more contexts than it used to
earlier. For instance unused public members of private
inner classes get warned against beginning M6.

See bug# 201912
Comment 2 Mike Wilson CLA 2009-05-05 14:48:33 EDT 
Changing Version tag to something more believable.
Comment 3 Srikanth Sankaran CLA 2009-05-07 07:45:41 EDT 
(In reply to comment #1)
> No, the default values should be "warning" for both
> the settings you mention. You can confirm this by
> switching to a fresh workspace (File + Switch workspace ...
> and type in the name of a non-existent workspace) and
> looking for the default values of these settings
> there.

Hello, have you had a chance to double check this ? (I'll
wait for a couple of days before closing this as INVALID).
Comment 4 Srikanth Sankaran CLA 2009-05-08 01:11:31 EDT 
Closing this as INVALID since the defaults are actually that these
unused symbols are warned against. To verify, play with these settings
and set them to error. Then click on the restore defaults buttonm you
will see that these are restored to be warnings.
Comment 5 David Audel CLA 2009-05-14 11:52:59 EDT 
Verified for 3.5RC1