On Thu, 03 Nov 2011 18:22:49 +0100, Jonathan M Davis <[email protected]>
wrote:
On Thursday, November 03, 2011 09:22 Steve Teale wrote:
I see that Walter just fixed a typedef bug in 2.056, even though I was
just ticked of for even thinking of using one ;=)
He probably fixed it because it hasn't actually been given the axe yet,
but
it's definitely going to get the axe - and probably soon, since there
was some
discussion of wanting to remove (or at least deprecate) features that are
definitely going to be removed before gdc actually makes it into gcc so
that
the changes are less disruptive when they happen.
- Jonathan M Davis
I think we need to change the release policy to make that happen.
Honestly the half-life period for D code using the mainline dmd
is about a few weeks and is released on ~monthly base.
This is a heavy restriction to attract professional development.
Currently this is creates the unlucky situation of deferring useful changes
to some projected D3, while still breaking the D language all too often.
I think there's a lot to learn from http://python.org/download/releases/.
For example somebody changing from Python2.5 to 2.7 is anticipating
some breaking changes, not so much for a change from dmd2.053 to dmd2.056.
martin
