Pathing in the D ecosystem is generally broken (at least on windows)

[Walter Bright via Digitalmars-d]

On 9/26/2015 1:21 AM, Manu via Digitalmars-d wrote:
>> I'll leave that to the GDC and LDC teams.
>
> And right there is the problem as I see it, summarised in one sentence ;)
>
> If you take the D ecosystem as aggregate, these issues are just as
> much issues for the core dev team as they are for these couple of guys
> with a distinctly unfair burden.

Everything is unfair, but the idea behind having 3 compilers is there is no one 
right way to make a compiler. Me telling the LDC and GDC teams what to do and 
trying to be their manager is inappropriate.


> An example that comes to mind; I think one of the biggest technical
> problem in the D ecosystem right now is that LDC doesn't support CV8
> debuginfo writing. You might be one of the world's most qualified
> experts on that, would you consider adapting that work to LLVM?

The CV8 support in DMD is open source and the format of the CV8 records is 
readily apparent by reading that source code. There's nothing magical about it. 
It's about a thousand lines of code.

   https://github.com/D-Programming-Language/dmd/blob/master/src/backend/cv8.c

But you're asking me to become an expert on LLVM internals, which is a lot harder.

I'm flattered that you believe I am such a superman I can do leading edge work 
on three totally different modern compilers simultaneously, and work on the 
language design, run D conferences, do presentations on D, help people with the 
daily emails asking for help, write articles, etc. But I assure you I am not 
that good. Oh, and I'm asked to write an IDE, too. I got a sincere proposal 
yesterday that I write a gui D debugger. I suppose I could do that before lunch 
tomorrow!