> > While C might be fine and dandy for getting o.k. native code w/o too > > much implementation effort, I think that it might be worth the effort > > to implement a JIT compiler for the perl interpreter's intermediate > > language. Speaking of intermediate languages, is there any more concrete info on the C# IL than what's in the article? I'd like to know what would be involved in supporting it. -- John Tobey, late nite hacker <[EMAIL PROTECTED]> \\\ /// ]]] With enough bugs, all eyes are shallow. [[[ /// \\\
- Re: Stuff in core (was Re: date interface, on language (... Dan Sugalski
- Re: Stuff in core (was Re: date interface, on langu... Tim Bunce
- Re: Stuff in core (was Re: date interface, on langu... Ken Fox
- Re: Stuff in core (was Re: date interface, on l... Nathan Torkington
- Re: Stuff in core (was Re: date interface, ... Tim Bunce
- Re: C# (.NET) has no interpreters Joshua N Pritikin
- Re: C# (.NET) has no interpreters Ken Fox
- Re: C# (.NET) has no interpreters Kevin Scott
- Re: C# (.NET) has no interpreters Dan Sugalski
- Re: C# (.NET) has no interpreters John Tobey
- Re: C# (.NET) has no interpreters Ken Fox
- Re: C# (.NET) has no interpreters Joshua N Pritikin
- Re: C# (.NET) has no interpreters John Tobey
- Re: C# (.NET) has no interpreters Joshua N Pritikin
- Re: Stuff in core (was Re: date interface, on l... Dan Sugalski
- Re: interpreter performance Joshua N Pritikin
- Re: Stuff in core (was Re: date interface, ... Randy J. Ray
- opcodes (was Re: Stuff in core (was Re: dat... Bradley M. Kuhn
- Re: Stuff in core (was Re: date interface, ... Ken Fox
- Papers and reference works Dan Sugalski