At 3:08 PM +0200 on 7/17/99, M. Uli Kusterer wrote: >>I think what he's after is something like CompileIt, which, using OTVar.h >>should not be too hard. > >Yup. But couldn't he take the JIT as a starting point? After all, it does >compile to machine-language, doesn't it? The JITC compiles to a machine language that can not be saved to disk. And it's slow, and does not support the new features in Intepreter. I would suggest starting with egcs. You get an optimizer and a real compiler to start with.
- Re: OODL: Goofball OT question Yennie
- Re: OODL: Goofball OT question Yennie
- Re: OODL: Goofball OT question DeRobertis
- Re: OODL: Goofball OT question Rob Cozens
- Re: OODL: Goofball OT question DeRobertis
- Re: OODL: Goofball OT question DeRobertis
- Re: OODL: Goofball OT question DeRobertis
- Re: Re: OODL: Goofball OT question Uli Kusterer
- Re: Re: OODL: Goofball OT question DeRobertis
- Re: Re: OODL: Goofball OT question M. Uli Kusterer
- Re: OODL: Goofball OT question DeRobertis
- Re: OODL: Goofball OT question Yennie
- Re: OODL: Goofball OT question M. Uli Kusterer
- Re: OODL: Goofball OT question DeRobertis
- Re: OODL: Goofball OT question Yennie
- Re: OODL: Goofball OT question Rob Cozens
- Re: OODL: Goofball OT question DeRobertis
- Re: OODL: Goofball OT question M. Uli Kusterer
- Re: OODL: Goofball OT question DeRobertis
- Re: OODL: Goofball OT question Michael Fair
- Re: OODL: Goofball OT question M. Uli Kusterer
