Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 334829

Summary:	SWT has many indirect accesses to static members
Product:	[Eclipse Project] Platform	Reporter:	Carolyn MacLeod <carolynmacleod4>
Component:	SWT	Assignee:	Carolyn MacLeod <carolynmacleod4>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	Silenio_Quarti
Version:	3.7
Target Milestone:	3.7 M5
Hardware:	All
OS:	All
Whiteboard:

Description Carolyn MacLeod

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

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