Live data from Hacker News

A Lisp in 99LOC

github.com

21–28 of 28 posts

Re: A Lisp in 99LOC

#21
post #15

Earlier quoted context omitted.

Certainly not the worst I have seen, by far; but yes, not pretty. IMHO “Just for making it shorter“. I would very much prefer 200 lines of actually readable nice code.

For reading, I enjoyed fe, which was very clear: https://news.ycombinator.com/item?id=36239175

Yes! Exactly what I meant. 700 lines, but of code that can be understood, and looks clearly as C. Also btw, the general file structure, the documentation, I prefer fe any day of the week. Thanks for pointing that out, I will take a look at it.

Re: A Lisp in 99LOC

#22
post #12

Earlier quoted context omitted.

Yeah. It's munged to fit in 99 lines.

That's besides my point, which is why I said "structure, not just expression". It could've used a struct rather than wedging tags into a double's first byte and still be 99 lines.

That's a standard technique in interpreters. All non-toy Javascript engines use it, for example.

Re: A Lisp in 99LOC

#24
post #17
post #9

Lisp in ~100 lines of Python: https://flownet.com/ron/l.py

Can’t you just “import lisp”?

Um, no?

    Python 3.11.6 (v3.11.6:8b6ee5ba3b, Oct  2 2023, 11:18:21) [Clang 13.0.0 (clang-1300.0.29.30)] on darwin
    Type "help", "copyright", "credits" or "license" for more information.
    >>> import lisp
    Traceback (most recent call last):
      File "", line 1, in 
    ModuleNotFoundError: No module named 'lisp'

Re: A Lisp in 99LOC

#25
post #12

Earlier quoted context omitted.

Yeah. It's munged to fit in 99 lines.

That's besides my point, which is why I said "structure, not just expression". It could've used a struct rather than wedging tags into a double's first byte and still be 99 lines.

Nan-boxing is awesome.

Re: A Lisp in 99LOC

#27
post #13
post #3

Holy cow this is —structurally, not just expression— some of the worst C code I have ever seen, with the abuse of the 'double' type, 'T' cast that looks like a declaration, endian dependency, and strict aliasing violations galore… does this even work on a modern compiler? o.O

Surpringly readable though, despite all that, if you've ever implanted a language in similar constraints.

*implemented.

Too late to edit now.

Post reply on HN