On 01/11/2011 07:17 PM, Jonathan M Davis wrote:
> Renaming a function and having a deprecated alias to the old name for a few
> releases eases the transition would definitely be good practice. aliasing a
> function just to have another name for the same thing wouldn't be good
> practice.
> There has to be a real benefit to having the second name. Providing a smooth
> deprecation route would be a case where there's a real benefit.
How about wrapping the aliases up in, e.g., std.compatibility.{c,
javascript, python, …}
Well, maybe not in std; that might imply a commitment to keep up-to-date
full library compatibility forever. But it might make a semi-useful
contrib library.
--Joel
