[PATCH] Expanded quoting rules for the assembler, fixed escaped quotes
Files patched: Parrot/Assembler.pm - Changed 'replace_string_constants' to patch the quoting t/op/build.t - Added tests, reordered the quoting. -- --Jeff [EMAIL PROTECTED]
Re: JIT compilation
There is an effort to compile ruby to the CLR, I don't know more, because I can't read japanese :-) And there is someone working on python support in the mono compiler, too. BTW: we just got our compiler running on linux and compiling a simple program, hopefully by next week it can be used for some more real code generation. lupus I know, I follow the mono list too. I don't doubt that dynamic languages can't be implemented on the clr, like I said, experience shows that it can be done on the jvm which is more restricting, what I'm not sure (and I don't think that there are precedents for this) is that they can be efficient when implemented on the clr. Benoit
Re: JIT compilation
On 11/17/01 Dan Sugalski wrote: BTW: we just got our compiler running on linux and compiling a simple program, hopefully by next week it can be used for some more real code generation. Yahoo! Congrats. Are we still slower than you are? :) It's a couple of months I'm in features-and-correctness mode, so I guess the current mono interpreter is slower than parrot: we have a design to make it twice as fast as it is now, but it would be a waste of time since with the JIT we are at least 30-40 times faster anyway :-) lupus -- - [EMAIL PROTECTED] debian/rules [EMAIL PROTECTED] Monkeys do it better
