|time to write a compiler firstname.lastname@example.org (1990-10-31)|
|time to write a compiler email@example.com (1990-11-05)|
|Re: time to write a compiler firstname.lastname@example.org (1990-11-06)|
|Re: time to write a compiler email@example.com (1990-11-06)|
|Re: time to write a compiler firstname.lastname@example.org (1990-11-07)|
|Re: time to write a compiler bright@nazgul.UUCP (1990-11-08)|
|Re: time to write a compiler email@example.com (1990-11-09)|
|Re: time to write a compiler firstname.lastname@example.org (1990-11-09)|
|From:||bright@nazgul.UUCP (Walter Bright)|
|Date:||8 Nov 90 02:36:00 GMT|
In article <1990Oct31.email@example.com> firstname.lastname@example.org (Roman Salvador) writes:
< I would like to find out the time it takes (more or less) to write a
<compiler (i.e. a Fortran 90 one). ...
It pretty much depends on if you are writing a research toy or plan to
sell the compiler. If you plan on selling it, triple all times you expect.
>From personal experience, I started writing a C compiler in 1982. 2 years
later, it was shipped (Datalight C). I have been working on it steadilly
ever since. It will never be finished.
A global optimizer takes 1 year to write, and then 1 year to debug out in
the field. Some companies never get it to work reliably :-).
A C compiler is about twice as complex as a Pascal compiler. C++ is twice
as complex as C. Starting from a working C compiler, it takes 1 to 2 years
to add C++ capability to it.
Return to the
Search the comp.compilers archives again.