Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 334829 - SWT has many indirect accesses to static members
Summary: SWT has many indirect accesses to static members
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.7   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: 3.7 M5   Edit
Assignee: Carolyn MacLeod CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-19 14:36 EST by Carolyn MacLeod CLA
Modified: 2011-01-19 14:37 EST (History)
1 user (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 Carolyn MacLeod CLA 2011-01-19 14:36:18 EST 
Go to Window -> Preferences -> Java -> Compiler -> Errors/Warnings
and select "Warning" for "Indirect access to static member".
Recompile.

There will be many (maybe 1000, depending on platform) warnings in the org.eclipse.swt project.

Some examples of these are:
- we moved PTR_SIZEOF from OS up into class C, and most references to PTR_SIZEOF are still in OS
- simple array alloc/free/movemem were also moved up into class C
- non-COM classes started using simple VtblCalls, so that was moved from COM up into OS, but most references are still to COM
- etc

This does not look good for people who have this warning turned on and they load org.eclipse.swt.
Comment 1 Carolyn MacLeod CLA 2011-01-19 14:37:49 EST 
Fixed > 20110119

We have decided that, for now, we prefer to simply ignore this warning,
so we have added the following line to
the /org.eclipse.swt/.settings/org.eclipse.jdt.core.prefs file:
org.eclipse.jdt.core.compiler.problem.indirectStaticAccess=ignore