- Pharo-dev - lists.pharo.org

Re: [Pharo-project] us can has mc2?

by StÃ©phane Ducasse

yes Stef On Apr 9, 2009, at 9:24 AM, Oscar Nierstrasz wrote: > > Sounds reasonable. > > Nevertheless, it should be flagged somewhere. Should it be an issue, > or should it be on one of the wiki pages? > > I searched, but found nothing. > > Is this the right page? > > http://code.google.com/p/pharo/wiki/ToDoBetterOnLongTerm > > - on > > On Apr 9, 2009, at 8:54, StÃ©phane Ducasse wrote: > >> >>> >>> Hi Folks, >>> >>> Are there plans to integrate Monticello 2 into Pharo? (I could not >>> find an issue in the Pharo issues database.) >>> >>> I understand from Lukas that most of the bootstrapping issues have >>> been resolved. Is anyone on this topic? Is there a good reason to >>> stick with the old MC? >> >> -support >> -open and public repository aka SS2 >> -understanding >> -process >> -tools >> >> at least for me. >> So we will but not now our plate is quite full. >> >> Stef >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

April 9, 2009

Re: [Pharo-project] Fwd: Re: FFI in closure image/modifying block arguments

by StÃ©phane Ducasse

ok Stef On Apr 9, 2009, at 9:22 AM, Torsten Bergmann wrote: > Hi Stef, > > if you integrate my latest change for ScriptLoader (see pharo inbox > ScriptLoader-...804.mcz) into the update stream there will be a > > ScriptLoader loadFFI > > method always loading the latest FFI. Until Alien/Alien FFI merge > is ready there should at least be an easy way to load and use FFI. > (loading is not enough, one needs to initialize ExternalType > and compileAllFields in ExternalStructure). > > Bye > T. > -- > Psssst! Schon vom neuen GMX MultiMessenger gehÃ¶rt? Der kann`s mit > allen: http://www.gmx.net/de/go/multimessenger01 > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

April 9, 2009

Re: [Pharo-project] us can has mc2?

by Oscar Nierstrasz

Sounds reasonable. Nevertheless, it should be flagged somewhere. Should it be an issue, or should it be on one of the wiki pages? I searched, but found nothing. Is this the right page? http://code.google.com/p/pharo/wiki/ToDoBetterOnLongTerm - on On Apr 9, 2009, at 8:54, StÃ©phane Ducasse wrote: > >> >> Hi Folks, >> >> Are there plans to integrate Monticello 2 into Pharo? (I could not >> find an issue in the Pharo issues database.) >> >> I understand from Lukas that most of the bootstrapping issues have >> been resolved. Is anyone on this topic? Is there a good reason to >> stick with the old MC? > > -support > -open and public repository aka SS2 > -understanding > -process > -tools > > at least for me. > So we will but not now our plate is quite full. > > Stef > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

April 9, 2009

[Pharo-project] Fwd: Re: FFI in closure image/modifying block arguments

by Torsten Bergmann

Hi Stef, if you integrate my latest change for ScriptLoader (see pharo inbox ScriptLoader-...804.mcz) into the update stream there will be a ScriptLoader loadFFI method always loading the latest FFI. Until Alien/Alien FFI merge is ready there should at least be an easy way to load and use FFI. (loading is not enough, one needs to initialize ExternalType and compileAllFields in ExternalStructure). Bye T. -- Psssst! Schon vom neuen GMX MultiMessenger gehÃ¶rt? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger01

April 9, 2009

[Pharo-project] Fwd: Re: FFI in closure image/modifying block arguments

by Torsten Bergmann

Stef wrote: >where is this package? http://source.squeakfoundation.org/FFI.html -- Neu: GMX FreeDSL Komplettanschluss mit DSL 6.000 Flatrate + Telefonanschluss fÃ¼r nur 17,95 Euro/mtl.!* http://dslspecial.gmx.de/freedsl-surfflat/?ac=OM.AD.PD003K11308T4569a

April 9, 2009

Re: [Pharo-project] us can has mc2?

by StÃ©phane Ducasse

> > Hi Folks, > > Are there plans to integrate Monticello 2 into Pharo? (I could not > find an issue in the Pharo issues database.) > > I understand from Lukas that most of the bootstrapping issues have > been resolved. Is anyone on this topic? Is there a good reason to > stick with the old MC? -support -open and public repository aka SS2 -understanding -process -tools at least for me. So we will but not now our plate is quite full. Stef

April 9, 2009

[Pharo-project] us can has mc2?

by Oscar Nierstrasz

Hi Folks, Are there plans to integrate Monticello 2 into Pharo? (I could not find an issue in the Pharo issues database.) I understand from Lukas that most of the bootstrapping issues have been resolved. Is anyone on this topic? Is there a good reason to stick with the old MC? Cheers, - on

April 9, 2009

Re: [Pharo-project] Closure compiler

by StÃ©phane Ducasse

>> >> New name: yes. > > Umm... HannanCompiler (after the original author?). umm..... rot and dead compiler that marcus resurrected Stef

April 9, 2009

Re: [Pharo-project] Fwd: Re: FFI in closure image/modifying block arguments

by StÃ©phane Ducasse

where is this package? Stef On Apr 8, 2009, at 10:23 AM, Torsten Bergmann wrote: > Stephane wrote: >> we already fixed a lot of occurrences of arg assignments and >> we should be soon able to recompile the entire pharo image. > > Nice - and it looks like Andreas also fixed FFI in "FFI-Kernel-ar. > 9.mcz". > > Thanks! > > Bye > T. > -- > Psssst! Schon vom neuen GMX MultiMessenger gehÃ¶rt? Der kann`s mit > allen: http://www.gmx.net/de/go/multimessenger01 > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

April 9, 2009

Re: [Pharo-project] Closure compiler

by Michael van der Gulik

(note: cross-posted on newcompiler and pharo-project lists) On 4/9/09, Marcus Denker <denker(a)acm.org> wrote: > > On 08.04.2009, at 17:40, Michael van der Gulik wrote: >>> >> >> I wonder if it is worth splitting the NewCompiler (which really does >> need a better name) into two packages: the front end and the back end. >> > > New name: yes. Umm... HannanCompiler (after the original author?). > So for packages, we have NewParser, AST and the rest. > Where would we split? IRBuilder would be the best candidate, I'd say. I'll get back to you on this when I have stuff to contribute. I'd like to separate out the IR classes so I can use them without needing to install the rest of the compiler. Gulik. -- http://gulik.pbwiki.com/

April 9, 2009