|Using C as a back end email@example.com (Pred.) (2000-10-19)|
|Re: Using C as a back end firstname.lastname@example.org (Jim Granville) (2000-10-22)|
|Re: Using C as a back end email@example.com (Peter Gammie) (2000-10-22)|
|Re: Using C as a back end firstname.lastname@example.org (Friedrich Dominicus) (2000-10-22)|
|Re: Using C as a back end email@example.com (Joachim Durchholz) (2000-10-22)|
|Re: Using C as a back end firstname.lastname@example.org (jacob navia) (2000-10-22)|
|Re: Using C as a back end email@example.com (2000-10-22)|
|Re: Using C as a back end firstname.lastname@example.org (2000-10-23)|
|[27 later articles]|
|From:||Jim Granville <email@example.com>|
|Date:||22 Oct 2000 01:12:14 -0400|
|Organization:||Mandeno Granville elect|
> 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?
> I see the following pros and cons:
> 1. I don't have to learn about / write code generators for the various
> 2. "Tried'n'true" back end
> 3. Shorter time-to-market
> 1. Slower compilation (scan + parse occurs twice)
> 2. No control over new versions of the back end
> Have there been any work on good ways to transform one language into C
A number of compilers produce C, look at the Modula-2 FAQ for some.
Some also produce Java ( see the MHC work ).
A CON you missed is perhaps the main operational one : Debug
Connection back to the original Source. This will impact far more than
your 1. 2.
Does anyone know of work to solve this one ?
1) With modern PC's compile time is a complete non-issue,
( so much, that make is rather redundant )
2) Version control is not too risky - you can always archive/freeze
with any version of compiler.
Certainly, given the public domain nature of C's ( Borland,Watcom ) they
can make usefull 'assemblers'
======= 80x51 Tools & IP Specialists =========
[I disagree about compile time; most modern compilers are very slow. By
comparison, the Dartmouth Basic compiler running on a 1 mips machine could
compile most user programs in under 1/10 second, from RUN to when it started
Return to the
Search the comp.compilers archives again.