dragoncoder047

I forget what computer I was on when I took that screenshot... tried again using a Chromebook, not sure what the DPI is. 100% is fine now, but I get...

Well, the weird rendering artifacts may just be an result of Chromebooks just being generally trashy... especially ones from 2018. (Sorry, I just love to hate on Chromebooks. They're all...

Testing it with my game as a torture test it actually made it slower. Not sure why...

As a side note I still think you should keep the existing keyword mechanism (entry in lookup table) because then it allows you to associate meaning to a particular keyword...

> I don't think there's currently any other useful function for keywords. Well, you could do `&key` arguments. The algorithm I see would be to take the `:foo foo-value` pairs...

Perhaps that bit doesn't need to be fixed, but here's another weirdness that occurs when you use a quoted symbol as the function: uLisp: ``` > ('progn '('print 'foo) ('print...

There's one thing that your fix doesn't cover: ``` > (progn 'foo) foo > ('progn 'foo) Error: undefined: foo ``` I just made some changes that also fix the `'print`...

At the very least, the bug where if you quote `('progn)` it evaluates some of the forms twice, is going to have to be fixed. (on my fork it's sorta...

I just ran the entire test suite with the second "can't call a symbol" message rigged to crash my ESP32 instead, and it didn't crash. So I think it's pretty...

> Thanks for these comments. I've decided to incorporate some of the changes you've made to `eval()` to fix these in an interim release, and also try to fix your...