Adding D Editor Support

[John A. De Goes]

Robert Fraser Wrote:
> There's multi-line error messages (for example, if there's an ambiguous 
> overload), and occasionally messages don't have a line, just a file.

Crap.

Now it's easy enough to support a new style of error reporting, if the format is consistent, but not so easy when it's hard to break things down into a small number of patterns. Multiline errors are particularly difficult because it's often not apparent when they end, or what is the most important part of the message.

Without documentation on the format, the best I can do is to experiment with the compiler and try to elicit all possible errors/warnings. And hope they fall into a small number of consistent patterns (which seems likely given that all the errors I encountered so far matched the above patterns).

Anyone having inside knowledge of the format care to save me some time here? (Walter, you listening? :-)

Regards,

John