Migrating D front end to D - post Dconf

[Daniel Murphy]

"Jonathan M Davis" <jmdavisProg at gmx.com> wrote in message 
news:mailman.1222.1368325870.4724.digitalmars-d at puremagic.com...
> The big problem is when you need to compile
> the compiler. You have a circular dependency due to the compiler depending 
> on
> itself, and have to break it somehow. As long as newer compilers can 
> compiler
> older ones, you're fine, but that's bound to fall apart at some point 
> unless
> you freeze everything. But even bug fixes could make the old compiler not
> compile anymore, so unless the language and compiler (and anything they 
> depend
> on) is extremely stable, you risk not being able to compile older 
> compilers,
> and it's hard to guarantee that level of stability, especially if the 
> compiler
> is not restricted in what features it uses or in what it uses from the
> standard library.
>
> - Jonathan M Davis

My thought was that you ensure (for the foreseeable future) that all D 
versions of the compiler compile with the most recent C++ version of the 
compiler.