Hi all
if you want to help pharo, it would be good to:
- go over some of the messages I sent to the mailinglist and turn
some of the points
as issue
- from memory I see the extensions of keith of kernel
- the fixes of nicolas
- fixing Author initials to get real name instead + a license
- enhance DrDoc.
- Run SmallLint on some packages.
- take some issues and fix them.
- helping for the integration server.
This afternoon I will empty the inbox.
Marcus how can we help for the NewCompiler?
The next step seems to be to take the closure stuff of Eliot and
merge it into Pharo.
The problem is that we would need new VMs for that... and one can
not even start
to do anything until this is done.
So may be the first step is to
- check vm building who can build what
I imagine that we will have the same problem with the TTF and
freetype support.
Am'I correct?
in parallel
- make sure that NewCompiler is ready to replace the oldCompiler
Do you have a roadmap?
-> Eliot's closures in the image.
-> port NewCompiler to emit code for this closure implementation
-> clean up newcompiler. Remove non-closure hacks
-> Evaluate to use the old parser as an alternative frontend.
Marcus
--
Marcus Denker -- [EMAIL PROTECTED]
http://www.iam.unibe.ch/~denker
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
