On 4/9/09, Marcus Denker <denker@acm.org> wrote:
On 07.04.2009, at 21:50, Michael van der Gulik wrote:
On 4/8/09, Marcus Denker <denker@acm.org> wrote:
On 07.04.2009, at 16:31, Alexandr Batalshikov wrote:
Hi,
I see in pharo0.1-10268dev09.04.1.image:
Compiler class>>closureParserClass ^self error: 'not installed'.
That is right? How to install "closureParserClass"?
these are leftovers from the NewCompiler ClosureCompiler. We will clean this up soon.
What is the story with the NewCompiler? Does Pharo include it? Or are you moving to Eliot's modification of the old compiler with closure support?
We integrated Eliot's work into Pharo for now. The actual closure realization is different but similar, so there is no reason to not to use his. The old "ClosureCompiler" then will be renamed "NewCompiler" and fixed to generate code for Eliot's closures.
The NewCompiler is a bit more modular/easier to understand and butcher, we used in for many experiments already and we will definitly port it.
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. Later this year (or next) I plan to do some hacking on the NewCompiler for integration into SecureSqueak. I'll post something on the NewCompiler mailing list when I get that far; I'll try to contribute stuff back to the NewCompiler project so hopefully they'll percolate through to Pharo, Squeak and other users. Gulik. -- http://gulik.pbwiki.com/