Replies: 1 comment 1 reply
-
I suspect the problem is in that If you inspect that massive 46k line file, it does contain your compiled string correctly, but appears to also have a copy of the macro definition for some reason, which it is expanding and executing instead: I don't know enough about what |
Beta Was this translation helpful? Give feedback.
-
I have learned that I can use Quicklisp with JSCL as long as I only use it in compile-time, that is: using Macros.
The first use case I saw is here:
https://github.com/nilesr/jscl-react/blob/master/emoji-search/filter-emoji.lisp#L3
This code will compile and run successfully with
jscl:compile-application
, which is good.I have also made something using Quicklisp in macros and it works well.
But, this is true ONLY when I do not expose anything to the REPL.
Whenever I tried to use Quicklisp, even only inside macros, and not
export
ing it, there will be runtime error.e.g.,
main.lisp
bundle it (bundle.lisp taken from here #443 (comment)):
And then in the browser:
I thought macros were the runtime thing, so there won't be any problem? Still digging it.
Forgive me, I have to do a dumb-ass ping to your awesome people: @mmontone @nilesr
Beta Was this translation helpful? Give feedback.
All reactions