Hi, I have a Java project that has been leveraging the clojure RT object to use edn as config, in turn the edn may have clojure functions as values and other goodies, we were looking at throwing Graal at our project, and thinking we could switch out direct use of clojure RT and using sci to interpret instead. I am just having trouble finding the core entrypoint to bootstrap sci .. so that I could eventually call

sci.core$eval_string_STAR_.invokeStatic(sciCtx, code) or sci.core$eval_string(code)

Check out Clojure’s Java API: https://clojure.github.io/clojure/javadoc/

I think it’s also possible to make one function in Clojure to do your SCI config and then use genclass to make it available to Java

Those are your two options

thanks - and sticking to the constraints of sci .. should make Graal a possibility

@gmercer note that you can also make clojure.lang.RT available in SCI, I'm not sure why you were using that

but programming against clojure.lang.RT is not recommended, as its basically an implementation detail of Clojure, not intended as an API

@borkdude probably old school stackoverflow examples .. unfortunately, I am still getting Graal defining class from bytecodes not supported, desperately combining over babashka to see how it is done 😉

@gmercer if you need any help on closed source code I can also come on to a call or something and you can pay me. if it's open source I could just take a look at the code. Just letting you know that this is a possibility :)

sometimes just using the flag --report-unsupported-elements-at-runtime can be helpful as graal may think you will hit something at runtime in the compiler which you actually don't