From: Matt Wette <matt.wette@gmail.com>
To: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: guile-user@gnu.org, Jeremiah@pdp10.guru, epsilon-devel@gnu.org
Subject: Re: You missed my later work
Date: Thu, 27 Apr 2017 16:51:03 -0700 [thread overview]
Message-ID: <F67883E2-58C8-4C6E-B18B-3BDE261A9C61@gmail.com> (raw)
In-Reply-To: <8760hqui0i.fsf@gnu.org>
> On Apr 27, 2017, at 5:55 AM, Jan Nieuwenhuizen <janneke@gnu.org> wrote:
>
>
> [cc: Matt, author of Nyacc]
>
>> Well now you could have told them we already had the forth
>> https://github.com/oriansj/stage0/blob/master/stage2/forth.s
>> but none of the people in the forth community bothered to build upon it
>
> You created a fully bootstrappable LISP and FORTH, wow!
>
> That would make my answer easier; I started with Scheme/Lisp because
> you have to start somewhere, and I like that better.
>
>> For example break up the C compiler problem into pieces, for example
>> have a seperate C preprocessor, a single file C compiler that only
>> produces assembly and just leverage the already existing assembly
>> infrastructure I already made.
>
> That could open up new possibilities. However, there are so many
> choices, is this going to help us get forward right now?
>
>> I honestly feel that is absolutely something that has to be done.
>> However, you'll have to constrain yourself to what language features in
>> C that you use to make the path from what I have completed to what is
>> required possible.
>>
>> Some questions I have are as follows:
>> 1) Could the C preprocessor componet of Nyacc be isolated and simplified
>> enough to run on stage0's lisp interpreter and solve the C preprocessor
>> question?
>
> @Matt: would separating the cpp part from Nyacc be feasible? Do you
> also think that's helpful?
>
Not sure what you are asking. Do you want a standalone CPP or a CPP-less C parser?
next prev parent reply other threads:[~2017-04-27 23:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-31 20:28 You missed my later work Jeremiah
2017-03-31 21:48 ` Jan Nieuwenhuizen
2017-03-31 23:17 ` Jeremiah
2017-04-27 12:55 ` Jan Nieuwenhuizen
2017-04-27 23:51 ` Matt Wette [this message]
2017-05-01 1:02 ` Jeremiah
2017-05-02 6:17 ` Next steps for Mes, stage0+? -- " Jan Nieuwenhuizen
2017-05-02 18:26 ` Jeremiah
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=F67883E2-58C8-4C6E-B18B-3BDE261A9C61@gmail.com \
--to=matt.wette@gmail.com \
--cc=Jeremiah@pdp10.guru \
--cc=epsilon-devel@gnu.org \
--cc=guile-user@gnu.org \
--cc=janneke@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).