Excellent! We should really get the NewCompiler because it will remove a lot of cruft too (SyntaxError as subclass of String and the like). I have the impression that we should prepare to load the newcompiler as soon as pharo one is ready and get the release time to really only us the NewCompiler. Stef
hi guys (and marcus in particular)
I'm at RMLL and we are discussing with mike about infrastructure for pharo. I will summarize some of the discussions in the following posts.
Mike suggested that we really use the NewCompiler for Pharo. Marcus can you comment on that.
What is missing is -> bootstrapping. But this is easy to fix.
Else there are some bugs that need to be fixed (e.g. when evaluating in the debugger, temps are sometimes not bound correctly). And the error-messages of the SmaCC parser need to be carefully evaluated of they work on practice. (Mathieu improved them last year).
Else we used it a lot and it seems to work.
Marcus
-- Marcus Denker -- denker@iam.unibe.ch http://www.iam.unibe.ch/~denker
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project