evolution

[Bill Baxter]

On Sun, Oct 19, 2008 at 3:17 PM, ore-sama <spam at here.lot> wrote:
> Andrei Alexandrescu Wrote:
>
>> Walter suggested that I move the
>> old modules in etc/, so changing e.g. std.algorithm to etc.algorithm
>> should make legacy code work.

A nicer way to do it would be to make it all deprecated (but still
operational) in one release, then replace it in the next release.

> may be std.old.*?

I like that better than etc.

Maybe even std.deprecate.*
Or
std_deprecated.*
(I think a package name can't be a keyword, right?  If it could then
I'd say std.deprecated.*)

I don't like etc though -- it doesn't imply to me at all that the
stuff inside it would be old and deprecated.

--bb