Is D 0.163 D 1.0?

[Kent Boogaart]

I've only just joined in the D community and have quite a few suggestions to 
make (and I believe they are all good ones). Whilst I don't want a 1.0 
release to be held up by me - as important as I am :) - I would like to 
understand how future D releases will handle breaking changes. For example, 
will breaking changes be avoided at all cost a la C++ / Java or will there 
be leeway so that the language doesn't evolve into a plethora of deprecated 
APIs and bad practices to avoid (again, a la C++ / Java).

Kent Boogaart


"John Demme" <me at teqdruid.com> wrote in message 
news:e9usak$eag$1 at digitaldaemon.com...
> Gregor Richards wrote:
>
>> clayasaurus wrote:
>>> Dave wrote:
>>>
>>>> Walter Bright wrote:
>>>>
>>>>> I think the title says it all.
>>>>
>>>>
>>>> I say it's ready for 1.0.
>>>
>>>
>>> vote++
>>
>> In my opinion it's unwise to make a point-oh release of anything
>> immediately after major, sweeping changes.  A few months more time for
>> people to submit major language change ideas before closing it up (which
>> I presume 1.0 would imply) would be a good idea.
>>
>>   - Gregor Richards
>
> A few more month's time for people to recommend changes!?!?  Phfff- we've
> being doing that for years!   IMO, we've got the features we need for D
> 1.0.  A few more bug fixes would be nice (#146) but those can be done 
> after
> 1.0.  More time for the new imports, sure, but no new features!  Let's do
> this already!
>
> -- 
> ~John Demme
> me at teqdruid.com
> http://www.teqdruid.com/