News for hackers. Stuff that matters.
Re:Crafting Interpreters: Calls and Functions by codr7 on Thursday July 25, 2019 @10:46AM (#20525797)
I'm all for more people creating their own languages, we've been riding on Lisp for quite a while now and I'm sure that's not the final answer to anything.

Didn't read this one, I don't have much time to read these days. But we definitely need more hands on practical information to counter the avalanche of academic fluff out there, and many seem to enjoy Crafting Interpreters.

Having spent 34 years writing code and around three years full time designing my own languages, most other kinds of code make me fall asleep sitting up these days. Nothing really compares to controlling your world from the outside.

Lately I've been working on a stack machine devkit [0] to use as foundation for new languages, providing convenient access to most of what's needed and an integrated assembler to control it from the outside. The general idea is that you link the library and hook in a custom reader for your syntax, possibly embedded as a separate opcode. It's 5kloc of reasonable MIT-licensed code, small enough to own.

Feel free to have a look and I'll try to answer any questions.

[0] https://github.com/codr7/cidk

Edit: Was it the academic toes? Because I'm just sharing some code I wrote to help people get started designing their own languages. What did you do for others without expecting anything in return lately?

Re:Crafting Interpreters: Calls and Functions by sctb on Thursday July 25, 2019 @11:49AM (#20526394)
Re your edit: you said that you didn't read the article and then started talking about yourself, which is rude.

https://news.ycombinator.com/newsguidelines.html

Re:Crafting Interpreters: Calls and Functions by danso on Thursday July 25, 2019 @12:24PM (#20526702)
I upvoted (and vouched, and starred the repo – thanks for sharing!), but I'm guessing you were downvoted because the first 2 grafs are easily misinterpreted as falling into the "I didn't read, but why is this thing necessary?" trope.

Deleting the 2nd graf would probably change the perception; it doesn't add any insight, and honestly, no one expects you or any commenter to have read the entire book before remarking on it.

Re:Crafting Interpreters: Calls and Functions by codr7 on Thursday July 25, 2019 @01:16PM (#20527339)
Thank you.

The point of the message as a whole and the code I shared was the opposite, we need more of this. I included the second paragraph as a disclaimer, I didn't read the book because I don't read much these days but I've heard great things about it.

Nah, there's just no way to protect yourself against this these days. I did absolutely nothing wrong here. But if you're looking for trouble and something to project your self loathing on, you'll find it. Ask and you shall receive.