Rename std.string.toStringz?
Jonathan M Davis
jmdavisProg at gmx.com
Sat Jun 25 19:42:50 PDT 2011
On 2011-06-25 19:21, Walter Bright wrote:
> On 6/25/2011 7:02 PM, Jonathan M Davis wrote:
> > The current plan at the moment when it comes to deprecation is that
> > things which are deprecated will generally be labeled as scheduled for
> > deprecation for 6 months, deprecated for 6 months, and then fully
> > removed - though the exact length may vary depending on release dates
> > and what exactly is being deprecated (e.g. stuff that's been around
> > longer is more likely to take longer to remove than stuff that's changed
> > after a single release - which hopefully happens very rarely). So, code
> > shouldn't be breaking out from under people, and they'll have some time
> > to make the necessary changes as best fits what they're doing.
>
> Using the deprecation mechanism to give people warning of breaking changes
> is good. But *still* we need to restrict breaking things only if we've got
> compelling, and I mean compelling, reasons to do so.
>
> We simply cannot build a D community on a mass of code that won't compile.
> Dsource is full of that.
And I agree. But I think that there are some things that need to be done
before we effectively freeze them. I don't think that the list is necessarily
long, but I do think that it needs to happen. That done, things _should_ be
effectively frozen.
- Jonathan M Davis
More information about the Digitalmars-d
mailing list