Hi andreas

this is clear. I really understand. This is why we asked mathieu to  
work on that and propose this project as SummerTalk project.
This would be great to have real exception too not subclass of String  
like in the default compiler for syntax error. :)
Mathieu already fixed a lot of things in the new compiler related to  
pragmas parsing. Now he is focusing
on the error handling and may be after he will work on the decompiler  
code.
If people wants to help we need the decompiler also working well.
Mathieu also worked on fixing the way comments are attached in the  
tree (before this was kind of random).
Stef

On 8 oct. 06, at 01:03, Andreas Raab wrote:

> Klaus D. Witzel wrote:
>> On Sun, 08 Oct 2006 00:35:19 +0200, Andreas Raab wrote:
>>> Not sure about this. There are issues with our current contexts,  
>>> BIG issues. So big that I'd very seriously consider accepting a  
>>> slowdown in exchange to fixing these problems.
>> :) Mathieu: hurry up, potential users are waiting for sensible  
>> performance comparisions :) Are there already benchmarks available  
>> for exhibiting the slowdown experienced with instance variables  
>> accessed from BlockClosures?
>
> I actually did a serious evaluation of the new compiler for the  
> last Croquet release. It failed the tests, primarily on the issue  
> of error messages. A compiler whose only complaint is "Token not  
> expected" is simply unusable no matter what else might be great  
> about it.
>
> Cheers,
>   - Andreas
>