Yes, that's a very good thought. Keeping wrappers around would be a good thing for groups like Rakudo that need them. I will try to add these tonight. These kinds of points would be very well to explicitly include in whatever new deprecation policies or processes that we adopt.
--Andrew Whitworth On Fri, Jun 18, 2010 at 10:46 AM, Andy Dougherty <[email protected]> wrote: > On Thu, 17 Jun 2010, Andrew Whitworth wrote: > >> I just merged the ns_func_cleanup branch into trunk. To recap: >> >> First part of the branch is renaming functions to follow proper naming >> conventions, and in some cases to be more accurate/descriptive about >> what they do: >> Parrot_get_namespace_keyed* -> Parrot_ns_get_namespace_keyed* > [ ... more similar sensible renamings ... ] > >> I'm going to start putting together a patch for Rakudo now, and maybe >> partcl too, if I have time tonight (tomorrow otherwise). If anybody >> else needs help with the update, let me know. > > I just read this mail and the "backward compatibility" mail thread in one > sitting, and had the following thought: > > This, of course, breaks Rakudo, and any other HLL using those functions, > and even though you are kindly fixing those, it will still make bisecting > around this change difficult. > > Would it be sensible to keep the old names around for a while as mere > wrapper functions for the new ones? Of course Rakudo could stick in a > bunch of #ifdefs to deal with the change, but I think the technical burden > should be parrot's in such things. > > -- > Andy Dougherty [email protected] > _______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
