On Wed, Oct 1, 2008 at 12:07 PM, Paolo Molaro <[EMAIL PROTECTED]> wrote:
> On 09/29/08 James Mansion wrote: > > Rodrigo Kumpera wrote: > > > These are shortcomings of the current AOT implementation of mono > > > that are easier to fix than implement a fast interpreter. > > Who said anything about fast? > > The mono interpreter already operated on a different internal > representation, not on IL code directly, so it's not jit-fast, > but still not as slow as Rodrigo would imply with his message. > > The main issue is that a few people showed interest in bringing the > intepreter back to life, saying it was important to them, but they never > dedicated 1 man hour to the task (or if they did, they didn't share the > code). > > So, if those people that claim an interpreter is importnat didn't dedicate > 1 man hour, why should we? (Note I'm not pointing figers to anyone here, > several people wanted an interpreter but were unwilling to spend > anything on it, money, man hours or anything else except email > postings:). > > Paolo has a good point, the mono team has other priorities, but if someone is willing to take up on bringing the interpreter back, just say so and we will sure give help and review the code. And if the idea is to have a small footprint interpreter, then ruling out CLR 2.0 would be advisable, as generics impose a significant footprint in terms of binary and runtime size. Cheers, Rodrigo
_______________________________________________ Mono-devel-list mailing list [email protected] http://lists.ximian.com/mailman/listinfo/mono-devel-list
