How to expose functions and macros to the REPL?

[VitoVan]

It seems that after jscl:bootstrap and jscl:compile-application, everything defined in my custom lisp file was disappeared from the final REPL.

I found an issue talked about this: #443

The solution in that issue does not suite me, since it bundled everything (include jscl itself?) and forbade the usage of #j:something.

[VitoVan]

I found a way to expose Lisp function to JS:

(setf #j:hello #'hello)

I don't know if this is the right way to do it (to expose Lisp function to JS), and this does not solve my problem.

[davazp]

@VitoVan right now there are two:

• Compile your application together with the rest of JSCL, as described the link.
• Don't compile your application, but include it as CL source and load it at runtime.

I'd like to have a third option where your application compiles into a your-app.js that is supposed to be loaded on top of the distributed jscl.js. But it is not very ready yet.

[VitoVan]

Option 1:

Compile your application together with the rest of JSCL, as described the link.

Sorry for my dumbness and poor interpretation ability.

Here is a working example: #443 (comment)

Do you mean this link?

jscl/src/compiler/compiler.lisp

Line 518 in 29885f7

;;; BOOTSTRAP MAGIC: We record the macro definitions as lists during

or the issue #443 itself?

I tried it again, it seems like to fail the usage of Quicklisp. I am still trying to figure it out.

Sorry for my dumbness and poor interpretation ability, again.

Now I think I know what you mean, but I got another problem with Quicklisp, trying to work it out. I will let you know if I made any progress.

Option 2:

Don't compile your application, but include it as CL source and load it at runtime.

I suppose this will forbade my usage of Quicklisp, is it?

Of course, Quicklisp won't work. It's a totally different question.

Option 3 (not yet):

your application compiles into a your-app.js that is supposed to be loaded on top of the distributed jscl.js

This is exactly what I am looking for. Can you provide some more tips other than #443 for me to give it a try?

Thank you for your reply, David. JSCL is great.

[davazp]

...and forbade the usage of #j:something
I'm not sure what you mean by that. #j: should still work with that approach. But it's true, it bundles your application and jscl.js together.

[VitoVan]

That is my mistake, I just tried again with #443 , it successfully bundled without error with #j: in my code.

It was some Macros and Quicklisp usage in my code caused problem.

[VitoVan]

I found something like this:

> (in-package :jscl)
> (let ((*environment* (make-lexenv)))
    (compile-application '("main.lisp") "main.js"))

from here: #427

But I can't use it with Quicklisp, like:

main.lisp

(eval-when (:compile-toplevel)
  (ql:quickload 'str))

(defun hello (name)
  (str:concat "Hello, " name))

It will compile, but will throw exception in the browser:

Uncaught No package STR

Which is totally understandable.

And I am still try to make it work, any help will be very appreciated.

[VitoVan]

Maybe it's like this:

If we want to expose a function that uses some package in Quicklisp, then we have to compile that package and it's all dependencies' dependencies' dependencies into JSCL.

That's shitty.

[VitoVan]

But we can use them at compile-time, that is: Using macros.

Like this:

https://github.com/nilesr/jscl-react/blob/master/emoji-search/filter-emoji.lisp#L3