mal VS paip-lisp

>Would be interesting to see how the interpreter works actually...

It's quite easy to see, there are interpeters for Lisp in like 20 lines or so.

Here's a good one:

https://norvig.com/lispy.html

(It has the full code in a link towards the bottom)

There's also this:

https://github.com/kanaka/mal

Here is one implementation of a lisp (mal specifically) in matlab: https://github.com/kanaka/mal/blob/dcf8f4d7b9cf7b858850a04a0...

Only 260 lines of code, pretty concise :)

have a look at the crafting interpreters book, plus make a lisp (lisp is a great first language to make a compiler/interpreter for, just google "lisp compiler/interpreter" and you'll find lots of resources)

If you're really okay with the limitations of a tree-walk interpreter, you might want to check out MAL, which will teach you how to write a tree-walk interpreter for a LISP. The code for MAL has been translated to most popular languages, so you can work through the creation of an interpreter in the language of your choice. JLox would give you a bit more detail and a more complex language, but I'm not convinced that it's all that important.

Write a small programming language (lisp (https://github.com/kanaka/mal) or brainfuck) in C++ to learn the syntax more. This will teach you a lot about programming languages in general.

So I started some hobbyist game dev using Unity and realised that the full process of making a game has dependencies on a mass of lower-level skills including lighting virtual environments. As a hobbyist photographer I could see some useful analogies from lighting studios and other scenes

So I pivoted, and eventually made money, not from selling a game, but from developing tutorials about digital lighting. I was also able to contribute to a project at work that was making a product based on commercial games engine, not by actually coding it, but by helping to better estimate the costs of the asset generation required.

Coding Unity object scripts in C# also got me back into programming, and I went on to successfully build a self-hosting lisp interpreter following the Make a Lisp guidelines [0].

[0] https://github.com/kanaka/mal/blob/master/process/guide.md

Hijacking the top comment to add https://buildyourownlisp.com and https://github.com/kanaka/mal

Have you seen https://stevelosh.com/blog/2018/08/a-road-to-common-lisp/ ? "Kludges" everywhere is applicable. On the other hand, having a function like "row-major-aref" that allows accessing any multi-dimensional array as if it were one dimensional is "sweeter than the honeycomb".

I still think CL code can be beautiful. Norvig's in PAIP https://github.com/norvig/paip-lisp is nice.

As for the inside-out remark, while technically you do it, you don't have to, and it's very convenient to not do. Clojure has its semi-famous arrow macro that lets you write things in a more sequential style, it exists in CL too, and there's always the venerable let* binding. e.g. 3 options:

    (loop (print (eval (read))))

PAIP by Peter Norvig, Chapter 23, Compiling Lisp

https://github.com/norvig/paip-lisp/blob/main/docs/chapter23...

Emacs is so much more than a text editor! But I need to stay on topic...

I believe your assessment of LISP (and therefore of MacArthy)'s impact on AI to be unfair. Just a few days ago https://github.com/norvig/paip-lisp was discussed on this site, for example.

Sounds like a great project idea to make a toy demo of this direction you'd like to see. Maybe comparable to https://github.com/norvig/paip-lisp/blob/main/docs/chapter15... and https://github.com/norvig/paip-lisp/blob/main/docs/chapter8.... which are a few hundred lines of Lisp each, but do enough to be interesting.

You could look into Paradigms of AI Programming by Peter Norvig which might interest you regardless of Lisp content.

Lisp has great power, examine PAIP, part II chapters 7 and 8.

A computer running Prolog reasons, and that only requires a couple of pages of code. So it seems feasible that the network could have learned some ability to reason within its network.

IMHO it's because lisp shines to manipulate symbols whereas the current AI trend is crunching matrices.

When AI was about building grammars, trees, developing expert systems builds rules etc. symbol manipulation was king. Look at PAIP for some examples: https://github.com/norvig/paip-lisp

This paradigm has changed.

Origen: Conversación con Bing, 4/4/2023(1) gigamonkey/monkeylib-binary-data - GitHub. https://github.com/gigamonkey/monkeylib-binary-data Con acceso 4/4/2023. (2) paip-lisp/chapter4.md at main · norvig/paip-lisp · GitHub. https://github.com/norvig/paip-lisp/blob/main/docs/chapter4.md Con acceso 4/4/2023. (3) bibliography.md · GitHub. https://gist.github.com/gigamonkey/6151820 Con acceso 4/4/2023.