Re:Why I wrote a book about interpreters
by agumonkey on Thursday December 01, 2016 @11:50AM
(#13080832)
Personal story only, I never liked Imp, nor OO that much (all my OO code tried to be lisp or caml without knowing it). I learned lisp eval, then lc, typed lc.. recently prolog; where the machine vanishes quite a lot. Yet the very high abstraction view that path led to makes the understanding of systems and languages very coherent even if thinking in an imperative POV. But I can't suggest doing that to anybody since it may fail miserably for them.
[ Parent
| on HN ]
Re:Why I wrote a book about interpreters
by nickpsecurity on Thursday December 01, 2016 @12:48PM
(#13081548)
Here's the one I always drop for people like you:
http://lambda-the-ultimate.org/node/1752
It stays low-level and builds the components of a Scheme at same time. Piece by piece with ability to understand and verify. The resulting language could be used to build better LISP's, ML's, Prolog's, etc. sklogic's DSL toolkit illustrates that nicely where he mix and matches on top of a foundation of a LISP custom-designed for it.
Taking it further, you might like FLEX and Ten15 VM that unified higher-level languages:
Re:Why I wrote a book about interpreters
by agumonkey on Thursday December 01, 2016 @12:52PM
(#13081607)
Heh, not my usual thinking habits, but I'll take a peek.
ps: the url is dead; https://web.archive.org/web/20100615153619/http://scheme2006...
Re:Why I wrote a book about interpreters
by nickpsecurity on Thursday December 01, 2016 @01:33PM
(#13082030)
It worked for me for some reason. Tested it before the post and just now. Good we have archive.org regardless to solve that problem. :)
Re:Why I wrote a book about interpreters
by agumonkey on Friday December 02, 2016 @03:43AM
(#13087093)
Sorry, I meant the last link of the article with the resources. The main link was fine you're right. https://web.archive.org/web/20100712083633/http://www.cs.ind...