Embed Notice

HTML Code

<blockquote style="position: relative; padding-left: 55px;"><section><a href="https://mastodon.social/users/mcc/statuses/114198121318573889">mcc (mcc@mastodon.social)'s status on Thursday, 03-Apr-2025 16:01:05 JST</a><a href="https://mastodon.social/@mcc" title="mcc@mastodon.social"><img src="https://gnusocial.jp/avatar/10951-48-20220921192024.webp" width="48" height="48" alt="mcc" style="position: absolute; left: 0; top: 0;">mcc</a></section><article><p>Oh my god. Oh my god??<br>So in this post <a href="https://mastodon.social/@mcc/114169299830195223" rel="nofollow">https://mastodon.social/@mcc/114169299830195223</a> i freak out at the fact my first-attempt 110-line LISP evaluator written off the cuff mostly worked. Then I realized it couldn't do nested expressions or function calls. Fine. Nesting turned out to require real changes!</p><p>Looked at function calls tonight</p><p>FUNCTION CALLS ALREADY WORKED. It worked when I made that post on the 16th. What didn't work was *tab characters*. By coincidence, my only test file containing a tab was the fn test.</p></article><footer><a rel="bookmark" href="https://gnusocial.jp/conversation/4837442#notice-9473402">In conversation</a><time datetime="2025-04-03T16:01:05+09:00" title="Thursday, 03-Apr-2025 16:01:05 JST">about 19 days ago</time> <span>from <span><a href="https://mastodon.social/@mcc/114198121318573889" rel="external" title="Sent from mastodon.social via ActivityPub">mastodon.social</a></span></span><a href="https://mastodon.social/@mcc/114198121318573889">permalink</a><h4>Attachments</h4><ol><li><label><a rel="external" href="https://gnusocial.jp/attachment/4407301">$ cat sample/test/basic/lisp/fun.ls0 
# Check if functions are being called (no args)
# Expect: 1 2
# Expect: 3 4(set 'do-print '(
	(set 'z x)
	(print z sp y ln)
))(set 'x 1)
(set 'y 2)
(do-print)(set 'x 3)
(set 'y 4)
(do-print)$ ./target/debug/lisp0 sample/test/basic/lisp/fun.ls0 
1 2
3 4</a></label><br><a href="https://files.mastodon.social/media_attachments/files/114/198/118/960/295/685/original/eabf1b9d1417c665.png" rel="external">https://files.mastodon.social/media_attachments/files/114/198/118/960/295/685/original/eabf1b9d1417c665.png</a></li><li><article><header><div>No result found on File_thumbnail lookup.</div><h5><a href="https://mastodon.social/@mcc/114169299830195223">mcc (@mcc@mastodon.social)</a></h5><div> from <span>mcc</span></div></header><div>*Blinks* I… hm.I just sort of wrote a LISP interpreter, mostly over two days. It is 110 lines long (the interpreter part; this is not counting the GC or the reader/parser). It felt suspiciously straightforward to write, I didn't like, *design* it, I was just like, yeah I've written an interpreter core loop before? Do that again but in Rust. It just sorta fell out.I am *terrified* by the question of what will happen if I attempt to run this.</div><footer></footer></article></li></ol></footer></blockquote>

Corresponding Notice

Embed this notice
mcc (mcc@mastodon.social)'s status on Thursday, 03-Apr-2025 16:01:05 JST mcc
Oh my god. Oh my god??
So in this post https://mastodon.social/@mcc/114169299830195223 i freak out at the fact my first-attempt 110-line LISP evaluator written off the cuff mostly worked. Then I realized it couldn't do nested expressions or function calls. Fine. Nesting turned out to require real changes!
Looked at function calls tonight
FUNCTION CALLS ALREADY WORKED. It worked when I made that post on the 16th. What didn't work was *tab characters*. By coincidence, my only test file containing a tab was the fn test.
In conversationabout 19 days ago from mastodon.socialpermalink
Attachments
1. $ cat sample/test/basic/lisp/fun.ls0 # Check if functions are being called (no args) # Expect: 1 2 # Expect: 3 4 (set 'do-print '( (set 'z x) (print z sp y ln) )) (set 'x 1) (set 'y 2) (do-print) (set 'x 3) (set 'y 4) (do-print) $ ./target/debug/lisp0 sample/test/basic/lisp/fun.ls0 1 2 3 4
  https://files.mastodon.social/media_attachments/files/114/198/118/960/295/685/original/eabf1b9d1417c665.png
2. No result found on File_thumbnail lookup.
  mcc (@mcc@mastodon.social)
  from mcc
  *Blinks* I… hm. I just sort of wrote a LISP interpreter, mostly over two days. It is 110 lines long (the interpreter part; this is not counting the GC or the reader/parser). It felt suspiciously straightforward to write, I didn't like, *design* it, I was just like, yeah I've written an interpreter core loop before? Do that again but in Rust. It just sorta fell out. I am *terrified* by the question of what will happen if I attempt to run this.

Public

Embed Notice

HTML Code

Corresponding Notice