On 16/07/2012 01:07, Walter Bright wrote:
On 7/15/2012 3:43 PM, Jonathan M Davis wrote:
On Sunday, July 15, 2012 15:30:57 Walter Bright wrote:
On 7/15/2012 3:27 PM, Jonathan M Davis wrote:
The problem is that we're still ironing out too much, and most of the
breakage relates to bug fixes, not new features.
There's been a lot of non-bug-fixing breakage, for example, renaming
library
functions.
Yeah, but those are always done through a deprecation path, so there's no
immediate breakage. And we've done most of that already, so that
should be
happening less and less.
It needs to stop completely.
No. It hasn't been made for no reasons.
But yes, some code is broken in the process. This is exactly why we need
a more sophisticated versionning process (note the recurring pattern in
my posts :D ).
The fact that some people have legacy code shouldn't stop D progress.
But with the current system, D must either break code or make no progress.
