3 ms·
I would and have suggested, to take basic logic gates and create a 'simple lisp' (what is that actually?) on top of those. It'll take you 'a while', but it's de
by tluyben2 15y ago
I would and have suggested, to take basic logic gates and create a 'simple lisp' (what is that actually?) on top of those. It'll take you 'a while', but it's definitely possible and after that you can simply count the logic gates you used. Strictly speaking the question is wrong ; what is a simple lisp, what features are required etc etc, then it's answerable by actually designing it from scratch with logic gates. Of course it also will depend on how good you are at actually implementing such basic systems; I've seen CPUs built from logic gates in college which had wildly different numbers of gates between the teams. You can do a crap job with anything ;) Still you would have an indication.
- _0ffh 15y agoYeah, that's basically doing the whole thing using specialised "lisp circuitry". Approaching the task from the other extreme, by just implementing the interpreter in microcode, would be much simpler - and I doubt that the end result would differ wildly in the number of gates used. I think this is basically a kind of minimal description length problem. And yes, you can do a crap job with anything ;) Edit: Btw. LISP 1.5 for the IBM 704 seems to be something like 10k lines of assembly code.