Thanks for the feedback. You know, this kind of feedback really motivates me towards making Descent more accurate, robust and stable. Now that D1 has settled and it isn't changing a lot, I think that's possible with time and patience.

By the way, I just uploaded a new nightly build which might have fixed some of those errors. For instance, in Tango I only have 9 errors, and in ddbi only 2. But to fix each of them is really time consuming... unfortunately...

I did a bit of Eclipse Plugin work before based on existing plugins and I know how frustrating it can be to try to extend the existing code base for your own needs. So, mucho respect, and keep them Descent versions coming!

I have to agree. I just updated and went from having random errors about the module statements at the top of my file including unicode escape sequences and the word "CLOSE" to near perfect semantic checks.
The only thing that's still wierd is that when I put "new ArraySeq!(SomeType)();", Descent seems to think the class is both abstract and final.

Descent has become my tool of choice for D development, and it seems to get better every time I turn around.