6 months ago • •
Oh, okay, secd and lisp are two distinct things, you might not be able to map your lisp perfectly with how secd does things.
If your plan is to run lisp on the secd vm, I'd really start with secd, it will advise how you will build your lisp on top.
@neauoire that makes sense, just needed to get this interpreter going after some failed attempts!
thank you for the advice!
Lo, thar be cookies on this site to keep track of your login. By clicking 'okay', you are CONSENTING to this.
Devine Lu Linvega
in reply to felipe • • •https://git.sr.ht/~rabbits/lispkit/tree/master/item/examples/greet.lisp
~rabbits/lispkit (master): examples/greet.lisp - sourcehut git
git.sr.htfelipe
in reply to Devine Lu Linvega • • •Devine Lu Linvega
in reply to felipe • • •Oh, okay, secd and lisp are two distinct things, you might not be able to map your lisp perfectly with how secd does things.
If your plan is to run lisp on the secd vm, I'd really start with secd, it will advise how you will build your lisp on top.
felipe
in reply to Devine Lu Linvega • • •@neauoire that makes sense, just needed to get this interpreter going after some failed attempts!
thank you for the advice!