Hello Ondrej,
Sorry for the delayed response:
----- Original Message -----
Hi Eric,
On Fri, Oct 6, 2017, at 12:16 PM, Eric Bavier wrote:
Hello Ondrej,
Thank you for the discussion.
On October 6, 2017 10:38:07 AM CDT, "Ondřej Čertík"
<ondrej@xxxxxxxxx>
wrote:
worth2) Is it simpler to implement Lisp in assembly or Lisp in
Forth?
If it's simpler in Forth, which it might be, then perhaps it
is
inmaintaining Forth, as an intermediate language between Lisp
and
assembly, even if overall it would be simpler to just maintain
Lisp
soassembly, because there are lots of Forth tutorials out there,
and
Forth.more people might be able to help with a Lisp implementation
in
or
I will maintain the stage0 FORTH as long as anyone feels it will
be
useful.
My hope is Lisp programmers will take my primitive lisp written
in
assembly and
use it only once to bootstrap a better lisp, written in lisp.
I kind of gave up, since I don't have the time to implementActually you could get it done in around 80ish hours of work.
Lisp in
Forth, and that's a lot of work.
But your hard work would be more beneficial writing FORTH
extending
leveraging our expanded FORTH.already
There is very little to gain from throwing away the work that
has
been done.stage0
I will assist any FORTH developer who wishes to contribute to
the
bootstrap (patches are always welcome)missed
But as a man to spent far too long writing programs in commented
Hex,
trust me when I say the lisp is fine but intentionally
primitive.
So please play with our expanded lisp and FORTH, find what we
have
and feel free to create anything you think will improve theor
bootstrap
secondary bootstraps.
Thanks. Just to make sure, I am not suggesting in any way that you
throw
away any of the hard work you have done. I am just trying to
understand
what's the best way to achieve bootstrap and whether to bother
with
Forth at all. It is currently unclear to me.
I have off and on been playing with implementing a C compiler in
Forth.
As a proof-of-concept I did the Rosetta Code "compiler" task in
Forth.
http://rosettacode.org/wiki/Compiler and repository at
https://notabug.org/bavier/rosetta-code-compiler-forth. Though
that
implementation runs on gforth, I tried to use only words that are
already
in stage0 forth or would be easy to port.
I haven't had time yet to expand this towards full C, but you seem
interested, so I thought I'd mention it.
I looked into your code, it looks very impressive. What needs to be
done
in order to compile TinyCC?
I also tried to run your code myself, but ran into some issues:
https://notabug.org/bavier/rosetta-code-compiler-forth/issues/1