On 11/28/2012 11:49 AM, deadalnix wrote:
On Wednesday, 28 November 2012 at 17:19:48 UTC, 1100110 wrote:
On 11/28/2012 07:31 AM, Jacob Carlborg wrote:
On 2012-11-28 13:46, Andrei Alexandrescu wrote:
Yep. Rails 4 breaks Rails 3 code. Not Rails 3.061 breaks Rails 3.060
code :o).
I've talked about that before. D doesn't have a versioning scheme that
makes any sense. It's just a number that gets incremented without any
meaning. Except that a greater number indicates a later version. Also
changes to the language, compiler, runtime and standard library always
happen in the same release.
I must admit that I'm surprised that no one has simply forked the
project in order to apply their own versioning scheme to it.
Well, D has been forked in the past (tango vs phobos) but it tended to
make things even worse.
Well I was thinking more along the lines of prevent breaking changes but
I suppose you are right.
And now that you mention it, I suppose I've forked the GC as well...
