> On Apr 27, 2017, at 5:55 AM, Jan Nieuwenhuizen <jann...@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?
