Rakudo build broken as of parrot RELEASE_2_10_1-633-ga3ca6c8

[Andy Dougherty]

On Wed, 1 Dec 2010, Peter Lobsinger wrote:

> On Tue, Nov 30, 2010 at 5:35 PM, Andy Dougherty <doughera at lafayette.edu> wrote:
> > Rakudo won't build with the current parrot master.  The first error
> > message is about the function 'Parrot_get_ctx_HLL_namespace'.  Were some
> > functions renamed?  If so, the old names should still be kept around as
> > wrappers for the new names, at least for a while.
> >
> > (Breakage like this makes it really hard to reliably bisect for important
> > changes.)
> 
> I get the sense there's an expectation that rakudo should always build
> and run cleanly against parrot head. I don't recall this ever being
> explicitly supported, and I think that it is not feasible in the
> general case (I do agree that in this specific case it would have been
> a possibility).

I was mainly addressing this specific case (and cases like this) where it 
would have been possible -- indeed relatively easy -- to not break things. 
(It would also have been consistent with the policy at 
http://trac.parrot.org/parrot/wiki/HowToDeprecate , though I understand 
not everyone agrees with that policy.)

In general, yes, stuff will get broken from time to time, but working to 
avoid the easily-avoidable nuisance breakage sends a good positive message 
to parrot's users that parrot developers value their time and efforts.

-- 
    Andy Dougherty		doughera at lafayette.edu