Mac Carbon VM 4.0.0b1 Closure Compiler Aware with Alien support

> Yes it compiles, yes after a bit of poking I could take a Squeak3.9-
> final-7067.image and build a closure aware image.
> No I could not do that without poking a bit, however I hope that we'll
> resolve the problems in a day or two.
>
> Yes, I could take a Pharo0.1Core-10243.image and after more poking
> could generate a closure aware Pharo image.
>
> At this time the 4.0.0b1 VM is not publicly available, another day or
> two of cross checking is required, I've asked the Pharo
> team to review my changes and the changes from Eliot. I've also asked
> Eliot to supply some fixes so we can recompile
> the  Squeak3.9-final-7067 image without problems.
>
> I cannot speak for the 3.10 or 3.11 images, other parties will need to
> pursue any work to make them closure aware.
>
> Tomorrow I'll poke at making the iPhone VM closure aware, however any
> iPhone image relies on the Pharo team resolving
> what the change sets should be to make the image closure aware.
>
> --
> =
> =
> =
> =
> =
> ======================================================================
> John M. McIntosh <[hidden email]>
> Corporate Smalltalk Consulting Ltd.  http://
> www.smalltalkconsulting.com
> =
> =
> =
> =
> =
> ======================================================================
>
>
>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>

> Hi pharoers
>
> what do we do with the closure compiler?
> Do we integrate it now or in 1.1
>
> Stef
>
> On Mar 3, 2009, at 6:48 AM, John M McIntosh wrote:
>
>> Yes it compiles, yes after a bit of poking I could take a Squeak3.9-
>> final-7067.image and build a closure aware image.
>> No I could not do that without poking a bit, however I hope that we'll
>> resolve the problems in a day or two.
>>
>> Yes, I could take a Pharo0.1Core-10243.image and after more poking
>> could generate a closure aware Pharo image.
>>
>> At this time the 4.0.0b1 VM is not publicly available, another day or
>> two of cross checking is required, I've asked the Pharo
>> team to review my changes and the changes from Eliot. I've also asked
>> Eliot to supply some fixes so we can recompile
>> the  Squeak3.9-final-7067 image without problems.
>>
>> I cannot speak for the 3.10 or 3.11 images, other parties will need to
>> pursue any work to make them closure aware.
>>
>> Tomorrow I'll poke at making the iPhone VM closure aware, however any
>> iPhone image relies on the Pharo team resolving
>> what the change sets should be to make the image closure aware.
>>
>> --
>> =
>> =
>> =
>> =
>> =
>> ======================================================================
>> John M. McIntosh <[hidden email]>
>> Corporate Smalltalk Consulting Ltd.  http://
>> www.smalltalkconsulting.com
>> =
>> =
>> =
>> =
>> =
>> ======================================================================
>>
>>
>>
>>
>> _______________________________________________
>> Pharo-project mailing list
>> [hidden email]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>
>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>

> Stef
> - Show quoted text -
> On Mar 3, 2009, at 6:48 AM, John M McIntosh wrote:
>
>> Yes it compiles, yes after a bit of poking I could take a Squeak3.9-
>> final-7067.image and build a closure aware image.
>> No I could not do that without poking a bit, however I hope that we'll
>> resolve the problems in a day or two.
>>
>> Yes, I could take a Pharo0.1Core-10243.image and after more poking
>> could generate a closure aware Pharo image.
>>
>> At this time the 4.0.0b1 VM is not publicly available, another day or
>> two of cross checking is required, I've asked the Pharo
>> team to review my changes and the changes from Eliot. I've also asked
>> Eliot to supply some fixes so we can recompile
>> the  Squeak3.9-final-7067 image without problems.
>>
>> I cannot speak for the 3.10 or 3.11 images, other parties will need to
>> pursue any work to make them closure aware.
>>
>> Tomorrow I'll poke at making the iPhone VM closure aware, however any
>> iPhone image relies on the Pharo team resolving
>> what the change sets should be to make the image closure aware.
>>
>> --
>> =
>> =
>> =
>> =
>> =
>> ======================================================================
>> John M. McIntosh <[hidden email]>
>> Corporate Smalltalk Consulting Ltd.  http://
>> www.smalltalkconsulting.com
>> =
>> =
>> =
>> =
>> =
>> ======================================================================
>>
>>
>>
>>
>> _______________________________________________
>> Pharo-project mailing list
>> [hidden email]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>
>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>

> Hi pharoers
>
> what do we do with the closure compiler?
> Do we integrate it now or in 1.1
>
> Stef
>
> On Mar 3, 2009, at 6:48 AM, John M McIntosh wrote:
>
>> Yes it compiles, yes after a bit of poking I could take a Squeak3.9-
>> final-7067.image and build a closure aware image.
>> No I could not do that without poking a bit, however I hope that  
>> we'll
>> resolve the problems in a day or two.
>>
>> Yes, I could take a Pharo0.1Core-10243.image and after more poking
>> could generate a closure aware Pharo image.
>>
>> At this time the 4.0.0b1 VM is not publicly available, another day or
>> two of cross checking is required, I've asked the Pharo
>> team to review my changes and the changes from Eliot. I've also asked
>> Eliot to supply some fixes so we can recompile
>> the  Squeak3.9-final-7067 image without problems.
>>
>> I cannot speak for the 3.10 or 3.11 images, other parties will need  
>> to
>> pursue any work to make them closure aware.
>>
>> Tomorrow I'll poke at making the iPhone VM closure aware, however any
>> iPhone image relies on the Pharo team resolving
>> what the change sets should be to make the image closure aware.
>>
>> --
>> =
>> =
>> =
>> =
>> =
>> =
>> =====================================================================
>> John M. McIntosh <[hidden email]>
>> Corporate Smalltalk Consulting Ltd.  http://
>> www.smalltalkconsulting.com
>> =
>> =
>> =
>> =
>> =
>> =
>> =====================================================================
>>
>>
>>
>>
>> _______________________________________________
>> Pharo-project mailing list
>> [hidden email]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>
>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

> Do the major VMs (Unix, Mac, Win) support this *now*?
> What is the required work to include the closure changes (are they
> published somewhere?)?
>
> I'd like to avoid that we get a dependency on VMs that would delay
> version 1.0. If everything is ready, though, I would also vote for
> including them now.
>
> Cheers,
> Adrian
>
> On Mar 4, 2009, at 17:25 , Stéphane Ducasse wrote:
>
>> Hi pharoers
>>
>> what do we do with the closure compiler?
>> Do we integrate it now or in 1.1
>>
>> Stef
>>
>> On Mar 3, 2009, at 6:48 AM, John M McIntosh wrote:
>>
>>> Yes it compiles, yes after a bit of poking I could take a Squeak3.9-
>>> final-7067.image and build a closure aware image.
>>> No I could not do that without poking a bit, however I hope that
>>> we'll
>>> resolve the problems in a day or two.
>>>
>>> Yes, I could take a Pharo0.1Core-10243.image and after more poking
>>> could generate a closure aware Pharo image.
>>>
>>> At this time the 4.0.0b1 VM is not publicly available, another day  
>>> or
>>> two of cross checking is required, I've asked the Pharo
>>> team to review my changes and the changes from Eliot. I've also  
>>> asked
>>> Eliot to supply some fixes so we can recompile
>>> the  Squeak3.9-final-7067 image without problems.
>>>
>>> I cannot speak for the 3.10 or 3.11 images, other parties will need
>>> to
>>> pursue any work to make them closure aware.
>>>
>>> Tomorrow I'll poke at making the iPhone VM closure aware, however  
>>> any
>>> iPhone image relies on the Pharo team resolving
>>> what the change sets should be to make the image closure aware.
>>>
>>> --
>>> =
>>> =
>>> =
>>> =
>>> =
>>> =
>>> =
>>> ====================================================================
>>> John M. McIntosh <[hidden email]>
>>> Corporate Smalltalk Consulting Ltd.  http://
>>> www.smalltalkconsulting.com
>>> =
>>> =
>>> =
>>> =
>>> =
>>> =
>>> =
>>> ====================================================================
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Pharo-project mailing list
>>> [hidden email]
>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>>
>>
>>
>> _______________________________________________
>> Pharo-project mailing list
>> [hidden email]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>

> sounds a good attitude.
> We should fix the rest of the items then.
>
> Stef
>
> On Mar 4, 2009, at 6:00 PM, Adrian Lienhard wrote:
>
>> Do the major VMs (Unix, Mac, Win) support this *now*?
>> What is the required work to include the closure changes (are they
>> published somewhere?)?
>>
>> I'd like to avoid that we get a dependency on VMs that would delay
>> version 1.0. If everything is ready, though, I would also vote for
>> including them now.
>>
>> Cheers,
>> Adrian
>>

> If the unix vm hasn't been updated with basic fixes or even critical
> fixes  for the last two years, why would you put it on the critical
> decision path?
>
> The macintosh VM is available now, and I'd guess a windows VM should
> be available since no-doubt qwaq has been building a windows one for
> bleeding edge deployment since
> all this work (and more) is being funded by qwaq.
>
>
> On 4-Mar-09, at 9:19 AM, Stéphane Ducasse wrote:
>
>> sounds a good attitude.
>> We should fix the rest of the items then.
>>
>> Stef
>>
>> On Mar 4, 2009, at 6:00 PM, Adrian Lienhard wrote:
>>
>>> Do the major VMs (Unix, Mac, Win) support this *now*?
>>> What is the required work to include the closure changes (are they
>>> published somewhere?)?
>>>
>>> I'd like to avoid that we get a dependency on VMs that would delay
>>> version 1.0. If everything is ready, though, I would also vote for
>>> including them now.
>>>
>>> Cheers,
>>> Adrian
>>>
>
> --
> =
> =
> =
> =
> =
> ======================================================================
> John M. McIntosh <[hidden email]>
> Corporate Smalltalk Consulting Ltd.  http://
> www.smalltalkconsulting.com
> =
> =
> =
> =
> =
> ======================================================================
>
>
>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>

> Yes it compiles, yes after a bit of poking I could take a Squeak3.9-
> final-7067.image and build a closure aware image.
> No I could not do that without poking a bit, however I hope that  
> we'll resolve the problems in a day or two.
>
> Yes, I could take a Pharo0.1Core-10243.image and after more poking  
> could generate a closure aware Pharo image.
>
> At this time the 4.0.0b1 VM is not publicly available, another day  
> or two of cross checking is required, I've asked the Pharo
> team to review my changes and the changes from Eliot. I've also  
> asked Eliot to supply some fixes so we can recompile
> the  Squeak3.9-final-7067 image without problems.
>
> I cannot speak for the 3.10 or 3.11 images, other parties will need  
> to pursue any work to make them closure aware.
>
> Tomorrow I'll poke at making the iPhone VM closure aware, however  
> any iPhone image relies on the Pharo team resolving
> what the change sets should be to make the image closure aware.