Re: Self compiling compiler

From	rockbrentwood@gmail.com
Newsgroups	comp.compilers
Subject	Re: Self compiling compiler
Date	2016-08-22 15:56 -0700
Organization	Compilers Central
Message-ID	<16-08-004@comp.compilers> (permalink)
References	<16-03-013@comp.compilers> <16-05-006@comp.compilers> <16-05-008@comp.compilers>

Show all headers | View raw

On Wednesday, May 25, 2016 at 7:07:16 PM UTC-5, federat...@netzero.com wrote:
> ...use the February 1985 printout PDFs
http://www.softwarepreservation.org/projects/c_plus_plus

On Sunday, May 29, 2016 at 8:02:22 PM UTC-5, federat...@netzero.com wrote:
> I transcribed much of the version 1 PDF. It has to be cross-checked...

Done. Paul McJones posted the transcription of Version E from 1985 ...

http://www.softwarepreservation.org/projects/c_plus_plus/index.html#release_e

... 450 pages of printout verified against the 1986 so as to minimize diffs.
That resolves most of the 365 places printout got clipped and restores most of
the spaces and tabs.

Not all the files required for compilation were in the printout; stuff would
have to be scavenged from the 1986 version and pulled back -- if necessary --
to the earlier dialect. Neither version is in a C++ dialect recognized today.
It compiles itself and only the 1986 version has C files.

If interested in doing work on self-compiling compilers; picoc can be found on
the net -- a C interpreter. It is only about 4000 lines when in minimal
configuration. However it is (self-described) legacy code and serious recoding
and redesign of the data structures will be needed; particularly to remove the
"God" objects that the entire parser; stack frame and lexer states were each
wrapped up in. The parser is recursive descent with backtracking. But the
grammar processed by it is not large enough to allow the interpreter to run
itself. A large part of the complication is that it uses no byte-code
compiling (but yet you gotta do something with the function bodies and loop
bodies -- you'll have to look and see how it's handled.)

Back to comp.compilers | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

Self compiling compiler ERSHC <ershc123@nyc.rr.com> - 2016-03-31 03:54 +0000
  Re: Self compiling compiler Kaz Kylheku <545-066-4921@kylheku.com> - 2016-03-31 15:01 +0000
  Re: Self compiling compiler Thomas Goorden <thomas.goorden@gmail.com> - 2016-03-31 17:50 +0200
  Re: Self compiling compiler "Nils M Holm" <nmh@t3x.org> - 2016-03-31 19:41 +0200
    Re: Self compiling compiler Kaz Kylheku <545-066-4921@kylheku.com> - 2016-04-03 10:34 -0400
      Re: Self compiling compiler Nils M Holm <nmh@t3x.org> - 2016-04-04 12:54 +0000
  Re: Self compiling compiler Thomas David Rivers <rivers@dignus.com> - 2016-03-31 14:16 -0400
  Re: Self compiling compiler alexfrunews@gmail.com - 2016-03-31 12:27 -0700
  Re: Self compiling compiler Jens Kallup <jkallup@web.de> - 2016-03-31 21:29 +0200
  Re: Self compiling compiler ERSHC <ershc123@nyc.rr.com> - 2016-04-02 20:58 +0000
  Re: Self compiling compiler federation2005@netzero.com - 2016-05-25 16:41 -0700
    Re: Self compiling compiler federation2005@netzero.com - 2016-05-28 14:49 -0700
      Re: Self compiling compiler rockbrentwood@gmail.com - 2016-08-22 15:56 -0700

csiph-web