Rakudo build broken as of parrot RELEASE_2_10_1-633-ga3ca6c8

[Moritz Lenz]

On 12/01/2010 01:45 AM, Andrew Whitworth wrote:
> On Tue, Nov 30, 2010 at 7:37 PM, Andy Dougherty <doughera at lafayette.edu> wrote:
>> No, not forever.
>>
>> My complaint here is that there was no "transition" at all. The new
>> function was not available to use before the old one was ripped out. If
>> there had been a transition time when both were available, an HLL could
>> start using the new function as soon as is convenient, and everything
>> would just work.  Your question is asking how long that transition time
>> should be.  I am merely saying it should definitely be longer than 0.
> 
> Okay, that makes good sense. If we put in the function names that
> Rakudo needs to keep building now, how long do we wait until we take
> them back out? After 2.11? After 3.0? Later?

What about only issuing deprecations after the alternative is available?
Then the current deprecation policy governs when the old name can be
removed.

> I only ask because we already have a problem where we are
> exporting--and supporting--far too many public symbols in libparrot,
> and adding in a bunch of transitional duplicates should be a temporary
> measure and not add to our long-term bloat.

Agreed. It shouldn't be long term, just medium term.

Cheers,
Moritz