Related articles |
---|
[2 earlier articles] |
Re: Compiler creation toolkit scholz.lothar@gmail.com (2008-06-11) |
Re: Compiler creation toolkit ang.usenet@gmail.com (Aaron Gray) (2008-06-11) |
Re: Compiler creation toolkit anton@mips.complang.tuwien.ac.at (2008-06-11) |
Re: Compiler creation toolkit rich@pennware.com (Richard Pennington) (2008-06-14) |
Re: Compiler creation toolkit scholz.lothar@gmail.com (2008-06-17) |
Re: Compiler creation toolkit scholz.lothar@gmail.com (2008-06-17) |
Re: Compiler creation toolkit bc@freeuk.com (Bartc) (2008-06-18) |
Re: Compiler creation toolkit theresistor@gmail.com (2008-06-20) |
Re: Compiler creation toolkit ademakov@gmail.com (Aleksey Demakov) (2008-07-05) |
Re: Compiler creation toolkit ademakov@gmail.com (Aleksey Demakov) (2008-07-05) |
From: | "Bartc" <bc@freeuk.com> |
Newsgroups: | comp.compilers |
Date: | Wed, 18 Jun 2008 19:03:06 GMT |
Organization: | Compilers Central |
References: | 08-06-018 |
Keywords: | C, tools |
Posted-Date: | 21 Jun 2008 12:56:43 EDT |
<scholz.lothar@gmail.com> wrote in message news:08-06-018@comp.compilers...
> My project is to create an eiffel like compiler.
> For the final optimized results i will generate c code, but i would
> like to use something else for faster updates in the edit-compile-run
> cycle.
I've found C compilers (even linkers) to be pretty fast now for reasonable
sized programs.
How slow would be your edit-compile-run cycle using C output? Or is the
bottleneck in your generation of C code?
What would be the output of your front-end anyway, if you don't use C?
--
Bartc
Return to the
comp.compilers page.
Search the
comp.compilers archives again.