Matthias Zenger

Thanks a lot for catching this bug, Brian! Have submitted your proposed fix.

The new releases of LispPad and LispPad Go have this bug fix included. Thanks for finding this issue!

Thanks for the bug report. Unfortunately, I am unable to reproduce it. Can you let me know what Xcode version you use, how you built LispKit, for what platform (iOS/macOS),...

I followed your instructions closely and could not reproduce the issue (see the transcript below). Both on an Intel and an M1-based MacBook Pro I could compile LispKit without problems....

Thanks a lot for the bug report! This is indeed pretty bad. Have just fixed the "division by zero" issues. It will take a few more weeks before this change...

The new releases of LispPad and LispPad Go fix this problem finally. Thanks for reporting the bug!

Hi Ben, here's an example how you can run a Scheme program via the .build/debug/LispKitRepl binary: ``` .build/debug/LispKitRepl -r Sources/LispKit/Resources --- Sources/LispKit/Resources/Examples/Channels.scm ``` `-r` is followed by potentially several arguments...

Closing this issue. Let me know if there is still something unclear.

If you care about performance then LispKit isn't really the right tool as it inherits quite a few performance penalties from Swift itself (e.g. it uses enumerations with associated values...

I would be happy to help fix this, but I would need more information: is your project an Xcode project? Do you use the Swift package manager? How did you...