DMD 1.030 and 2.014 releases
Chris Wright
dhasenan at gmail.com
Fri May 23 16:21:27 PDT 2008
Chris Wright wrote:
> Bill Baxter wrote:
>> Chris Wright wrote:
>>> Robert Fraser wrote:
>>>> Sean Kelly wrote:
>>>>> What worries me is that long
>>>>> asked-for bug fixes like this may be left out of DMD 1.0 as a way
>>>>> to "encourage" people to move to D 2.0. If that happens, I'm out.
>>>>
>>>> Indeed that's a fear I have as well. D 1.0 has never been fully
>>>> stable (look at the ".init" change that happened after 2.0 was
>>>> out... that broke a lot of code). So it seems rather arbitrary that
>>>> a bug fix like this (reported as bug, not an enhancement, before 2.0
>>>> was on the horizon) would only make it to the 2.0 branch.
>>>
>>> A lot of people have been annoyed by a lot of these changes.
>>> Unfortunately, nobody (and that includes the lack of me) has gotten
>>> off their butts to release a DMD 1.1.x branch.
>>
>> When you say "nobody" are you suggesting that the D community should
>> create a 1.1 branch and release it whether Walter wants it or not?
>
> I am. There seems to be demand for it. And if there were such a branch,
> Walter could even stop maintaining the 1.x branch because bugfixes from
> the 2.x branch would get ported to the 1.1 branch.
Though this is made harder since the DMD frontend isn't developed using
any version control system that I can access. So I can only see a whole
lump of changes between two dmd2 revisions, many of which are bugfixes,
many of which are changed features that will impact user code, and some
of which are actually nonbreaking features. Given the overhauls done to
const, it may be a better idea just to diff dmd1.030 and dmd2.014 and
start from there.
More information about the Digitalmars-d-announce
mailing list