Progress towards Exupery 0.12

Sebastian Sastre ssastre at seaswork.com
Sun Apr 29 23:33:46 UTC 2007


Good job Bryce. I know that it's just too soon to say but do you have any
glimpse of the stability of an image running wit exupery? There is any
version that could be stable enough to try it in production or it is too
soon?

Regards,

Sebstian
 

> -----Mensaje original-----
> De: exupery-bounces at lists.squeakfoundation.org 
> [mailto:exupery-bounces at lists.squeakfoundation.org] En nombre 
> de bryce at kampjes.demon.co.uk
> Enviado el: Domingo, 29 de Abril de 2007 15:55
> Para: exupery at lists.squeakfoundation.org
> Asunto: Progress towards Exupery 0.12
> 
> 
> All that's required is a little more debugging. This release 
> can compile in the background. The stress test runs again but 
> when Exupery starts compiling itself using the background 
> compiler after a few minutes it stops due to a bug. I'd like 
> to be able to run the background compiler for at least an 
> hour before releasing.
> 
> Exupery is probably more reliable now than it's been before. 
> The other part of this release has been fixing some old stack 
> tracing bugs. That introduced block finder bugs which have 
> been fixed along with some old block finder bugs. By the 
> standards of previous releases, it would be releasable now.
> 
> I'm thinking about freeing up the "unused" slot in 
> MethodContext so that Exupery can be loaded in an image 
> running the closure compiler without causing crashes. More 
> work would be required to compile closure compiler code.
> 
> Bryce
> _______________________________________________
> Exupery mailing list
> Exupery at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/exupery



More information about the Exupery mailing list