The compiler in eclipse can give a warning
if it sees code that references a static object
in a non-static context.
This seems like a sensible (if only occasionally useful)
Why should anyone want such a warning? Surely lots of code
references static objects in non-static contexts.
What this means is give a warning if you write,
where "bar" is a static method.
This is perfectly valid, but weird.
The eclipse compiler, and rightly so I think,
flags this as a warning.
feedback received and I agree with Tom on this one.
All gcj front end bugs have been fixed by the gcj-eclipse branch merge.
I'm mass-closing the affected PRs.
If you believe one of these was closed in error, please reopen it
with a note explaining why.