Polishing D - suggestions and comments

[Unknown W. Brackets]

Actually, I'm much more interested in basic things: proper highlighting 
that stays up to date with the language, basic syntax checking that 
really works, proper error file/line integration that doesn't suffer 
from pretty printing, etc.

This is from my experience trying to write a D highlighter/language 
service using the VSIP package for Visual Studio.

But really that's just a thought.  I would like to see D do something 
else "cool" other than just the language itself, but the other things I 
noted are (imho) much bigger issues.

-[Unknown]


Robert Fraser wrote:
> You mentioned IDEs a couple times, specifically in that they should be 
> able to access DMD via some sort of API. While this would be great, 
> Descent (in trunk, sadly the kinks are still being worked out...) takes 
> a different approach. We have a full Java port of the DMD semantic 
> front-end, which we are using to do things like display errors inline as 
> the user types. From working with Descent, I can say that having 
> programatic access to the AST would be nice, but since most advanced 
> IDEs would want to extend it anyway, it's a lot of work for a small gain.