|Using C as a back end firstname.lastname@example.org (Pred.) (2000-10-19)|
|Re: Using C as a back end email@example.com (Jim Granville) (2000-10-22)|
|Re: Using C as a back end firstname.lastname@example.org (Peter Gammie) (2000-10-22)|
|Re: Using C as a back end email@example.com (Friedrich Dominicus) (2000-10-22)|
|Re: Using C as a back end firstname.lastname@example.org (Joachim Durchholz) (2000-10-22)|
|Re: Using C as a back end email@example.com (jacob navia) (2000-10-22)|
|Re: Using C as a back end firstname.lastname@example.org (2000-10-22)|
|Re: Using C as a back end email@example.com (2000-10-23)|
|Re: Using C as a back end firstname.lastname@example.org (2000-10-23)|
|[26 later articles]|
|From:||Peter Gammie <email@example.com>|
|Date:||22 Oct 2000 01:17:50 -0400|
|Organization:||University of New South Wales|
Take a look at Simon Peyton-Jones et. al.'s work on Haskell -> C
Daniel Diaz's work on wamcc (do a google search), and the Mercury
project are both (basically) Prolog -> C mappings.
The biggest problem with compiling to C is its lack of
expressiveness; almost certainly you'll want to use gcc's extensions
(such as goto), unless your language is already close to C.
For a real challenge, try targetting the JVM. ;-)
> I have designed a language for which I'm hoping to create a compiler.
> Since I want a portable solution I was thinking about using a
> retargable C or C++ compiler in the back end along with appropriate
> assembler / linkers. Is this a good solution?
Return to the
Search the comp.compilers archives again.