Editor does not stop red underlining a class that has just been defined

[stevemessick]

Editor does not stop red underlining a class that has just been defined, if the first use of that class name is used in parameter to function.

For example, type this in exactly this order:

foo(thing) {

}

main() {
 foo(new Viking());
}

SAVE (notice that Viking is underlined)

Now type this at top of the file:

class Viking {

}

SAVE (notice that Viking is still underlined)

Hope that helps,
sethladd
////////////////////////////////////////////////////////////////////////////////////
Editor Version: 8124
////////////////////////////////////////////////////////////////////////////////////
OS: Mac OS X - x86_64 (10.6.8)
SDK installed = true
Dartium installed = true
AnalysisServer enabled = true
////////////////////////////////////////////////////////////////////////////////////

[jwren]

Set owner to @jwren.

[jwren]

I confirmed that this is still an issue on 11610 using the included steps.

Looked at the editor code and problems view code and think that this is a race condition. Sometimes in my runtime workbench the bug isn't there (consistently), but when I try a built version of the editor, I can consistently have the "no such type "Viking"" problem appear and disappear by adding and removing "class Viking{}", while having "new Viking()" underlined and not being redrawn.

Any ideas?

---

cc @devoncarew.
cc @stevemessick.

[jwren]

Issue is with Eclipse. Marking the issue as WontFix:

[Notes from Konstantin]
Because warning icon disappears from left band of editor (and from problems view too), this means that Analysis Server and AnalysisMarkerManager work correctly. What is probably not correct is removing and re-adding Decorations in org.eclipse.jface.text.source.AnnotationPainter.catchupWithModel(AnnotationModelEvent).

So, just to make sure. This is bug in Eclipse. I saw this with JDT too.

---

Added WontFix label.