Migrating dmd to D?

[Iain Buclaw]

On Mar 6, 2013 1:18 PM, "Iain Buclaw" <ibuclaw at ubuntu.com> wrote:
>
> On Mar 6, 2013 12:51 PM, "Minas Mina" <minas_mina1990 at hotmail.co.uk>
wrote:
> >
> > A big problem is that GDC and LDC in the distros are not up to date.
GDC was 2.058 I think. This has forced me to use dmd even for my final code
(I don't want to get in the trouble of building them by source, this is
ancient).
>
> One of the benefits of the merger would be that this would be a part
non-issue anymore, as all distros will (or should) ship gdc.
>
> However what won't happen is frontend updates following a release of gdc.
So eg: one release will come with 2.062 frontend, and 10 months later the
next release will come with 2.068, or whatever happens to be the current at
the time.
>

This also might be a time to re-address the minor release scheme that has
been discussed in the past (eg: 2.062.1, 2.062.2, etc).   Rather than focus
on maintaining a tree for each release of the D frontend implementation, we
pick a common release that gdc/ldc is shipped with, and pull in bug fixes
from main development and later releases.  When the shipped versions of
gdc/ldc get updated, we then start the process over from that new common
release (again, eg: 2.068) and start maintaining minor releases for that
(2.068.1, etc).

Regards
-- 
Iain Buclaw

*(p < e ? p++ : p) = (c & 0x0f) + '0';
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.puremagic.com/pipermail/digitalmars-d/attachments/20130306/d10f1c06/attachment.html>