(Possible) compatibility with Interlisp-D? #6
Replies: 3 comments
-
Greetings. LISPF4 is an interpreter and does not compile to a VM. It was implemented with access to no information other than the 78 IRM. Having a lot of experience with LISPF4 and some experience with Medley (interlisp.org), I can tell you there is a world of difference between the two. LISPF4 basically implements a reasonable subset of the 1978 spec (IRM). LISPF4 comes with a manual that enumerates what facilities it provides. There are no future goals I am aware of. |
Beta Was this translation helpful? Give feedback.
-
I am converting this issue to a discussion. |
Beta Was this translation helpful? Give feedback.
-
Can you make a percent estimate about how much of the IRM 1978 is implemented? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Currently I'm analyzing the Interlisp-D Fugue-2 release source code (~Aug. 1983) using the tools I built for this purpose (see https://github.com/rochus-keller/interlisp/). My intention is to eventually implement a VM and bootstrap for either the virtual image or the source code (whatever works).
While doing research I came across your interpreter. May I ask whether you have tried to make your interpreter compatible with the Interlisp-D source code? In the readme file you write that your interpreter supports a subset of Interlisp. I assume you refer to Interlisp-10, i.e. the version described in the 1978 IRM included in the repository. Is there a current specification of the subset, or should I derive it from the source code? Is full compatibility to the IRM (or possibly Interlisp-D) a project goal, or have there been attempts to do so? Is there any relation of this project with the "The Interlisp Virtual Machine Specification", Moore, 1976/1979?
Beta Was this translation helpful? Give feedback.
All reactions