You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, importing an external Wolfram package works but the new symbols are not, by nature, accessible from wolframite.wolfram (and so have to be executed using the deferred forms).
We could provide a library method for adding external packages seamlessly.
The two main options would be to either
use clj-intern (as I used previously on the realatoms project).
somehow update wolframite.wolfram or create a similar namespace file (that is accessible at runtime).
The text was updated successfully, but these errors were encountered:
wolframite.impl.wolfram-syms.write-ns/write-ns! could be perhaps hacked for this purpose but it may be cleaner with a dedicated fn. A question is whether users would want one ns file per package or a single one. Given namespacing needs, the former may be preferable?
Perhaps there could be a variant of load-package! which also writes (and loads) this ns...
A dedicated function would probably be best and I think 1 per package would be the cleanest, though Wolfram is somewhat weird about namespaces. A variant of load-package! would be great; manually writing lots of namespaces would, of course, be a pain.
Currently, importing an external Wolfram package works but the new symbols are not, by nature, accessible from wolframite.wolfram (and so have to be executed using the deferred forms).
We could provide a library method for adding external packages seamlessly.
The two main options would be to either
The text was updated successfully, but these errors were encountered: