"Bruno Medeiros" wrote in message news:[email protected]...
[snip]
I know that a lot of work needs to be done before the frontend is ready to
be efficiently used as a library, but that doesn't make it impossible.
But anyways, those are secondary points actually. What I think is really
crucial, is that we don't have a main-stream compiler in D. When DMD gets
ported to D, and the main development of DMD happens there, in the D
version, then I'll believe a reasonable compiler-as-library could happen.
I think you may have missed something! This is coming in the near future.
I have been working on automatically converting the DMD fronted to D since
dconf (and before). I've produced working compilers on win32, linux32, and
linux64, with the other platforms currently lacking only because I don't
have a box set up for them.
The only outstanding work for dmd is fixing layout and commenting/formatting
issues in the generated source, which I am slowly getting through.
I expect any issues encountered with the other platforms to be minor, and
hopefully switching gdc and ldc will be fairly painless too.
I'm hoping 2.066 will be the first D-based dmd release and work on the C++
source will cease immediately after that.
https://github.com/D-Programming-Language/dmd/pull/1980
https://github.com/yebblies/magicport2.git
> I disagree, this is 'the plan'. Please, go into detail, I would love
to
> find out about any roadblocks I've overlooked now rather than later.
What do you mean, are you going to invest a lot of work on that?
I already have!
"git log --merges | grep "\[DDMD\]" | wc -l" shows 217 merged pull requests
tagged as DDMD, and there were quite a few before I started tagging them.
Converting to D is the first step to getting compiler-as-a-library from dmd.
