All this talk about 1.0 makes me worried.

[Jeremy]

In article <e0901s$1fcd$1 at digitaldaemon.com>, Charles says...
>
> > I suppose many people like the idea of placing a stake in the ground ~
> > as means of marking/stamping progress?
>
>I know of alot of people ( myself partially included ) that are waiting 
>for a D 1.0 untill they really commit to using D.  Untill it reaches a 
>1.0 ( which feels like never -- in which case if it is going to take 
>another year or greater we should be talking about how to handle and 
>work with a perpetually changing language - id be curious to know how 
>often you have to update mango in response new DMD releases ) , i doubt 
>'corporations' would even consider using it.  Even post D 1.0 is going 
>to take a big effort from the community to get D in the mainstream.
>

I'd have to agree. There needs to be some v1.0 'base' that D programmers can
rely on to not change enough to break existing code... future changes could be
simply fixing bugs/feature additions etc.

For example, I cannot compile DWT with DMD v0.150 (can anyone else?) -- makes it
hard to develop libraries if no compatibility is really gaurenteed :(

Jeremy