On Mar 4, 2010, at 9:53 AM, Lukas Renggli wrote:
>>> I'll try to build the tests and come up with a better solution.
>>
>> You what I would love to spend 2/3 weeks just coding in the new compiler and
>> making sure
>> that it has the right abstractions/messages to deal with issue like that.
>
> The problem is that the New Compiler is not really in a better state
> than the old compiler. Of course it has more objects and is much
> easier to extend, but all in all it is a mess too. This is mostly due
> to the fact that the system below it changed quite a bit in the past
> years (pragmas, properties, closures, primitives, new bytecodes, ...)
> and that the New Compiler had to be patched and changed quite heavily
> to accommodate these new requirements that it was not designed for.
> Maintaining and fixing the New Compiler got so extremely expensive
> that it is questionable if this is still a viable platform? Ask Jorge
> and Marcus.
It needs work.... the problem is that I did not have any time and energy to work
on it. (traveling/moving and learning new languages are nice, but two time in
one year
was too much...).
But I *definitly* need the infrastructure... in some form. I need to get
Reflectivity to
work again, it's needed for at least Jorge's work and JB's work... and for
other research
on Reflection.
I plan to somehow allocate more energy to this the next weeks (and maybe scale
down on
Pharo bugfix harvesting. Note to self: Definitly I should not start any new
things in addition).
One thing that is clear: In general, having X things doing the same is not
going to work in the long run.
We need to concentrate to have one Ok instance of everything. This is true for
GUI toolskits, Parsers,
ASTs, Compilers, Browsers... Than we can iterate on this one thing to make it
better. Wasting engery to
maintain multiple instances of everything makes no sense.
Marcus
--
Marcus Denker -- http://www.marcusdenker.de
INRIA Lille -- Nord Europe. Team RMoD.
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
