Awesome work on the multimethod support!

thanks 🙂

My Github sponsors profile finally went live. If you're using babashka and/or sci and want to show your support, here's a way. Even if only for 1 dollar a month, it helps sustain these projects. https://github.com/sponsors/borkdude

FYI, another place where one can use Sci https://observablehq.com/@jeroenvandijk/untitled/5

wow, cool!

I have done it before with self-hosted Clojurescript which was hacky to get working. I think the interop features of Sci could make this quite interesting. Hopefully someone picks it up:)

where do you specify the dependency on sci?

or does require automatically pick the newest version from npm?

They proxy npm somehow

i think so

You can probably also specify versions. I played with it a longer time ago and don't remember. I was lucky enough to get my old example working with Sci in a few minutes 😎

pretty cool 🙂

I think so too!

And what's cooler than self-hosted clojurescript is that

cljs `(fn [a b] (+ a b))` 

some js -> sci interop in action

@borkdude first, thanks for creating babashka it's pretty awesome :)

i have a question about the usage with deps.edn. how can I pass on additional arguments? The following works in Clojure for JVM

clj -A:main -e some-option some-action

deps.exe -A:main -Scommand "bb -cp {{classpath}} {{main-opts}}"

okay, the new -- option that I read about in #tools-deps works!

deps.exe -A:main -Scommand "bb -cp {{classpath}} {{main-opts}}" -- -e some-option some-action

even without -- the above example should work I think

but great to hear that also worked for you and thanks for the compliment

actually i'm still not able to get it to work

❯ deps.exe -A:main -e foo bar                                                        
(-e foo bar)

❯ deps.exe -A:main -Scommand "bb -cp {{classpath}} {{main-opts}}" -e foo bar         
clojure.lang.ExceptionInfo: Could not resolve symbol: foo [at line 1, column 1]

the main does (println args)

❯ deps.exe -A:main -Scommand "bb -cp {{classpath}} {{main-opts}}" -- -e foo bar
(-- -e foo bar)

yeah, in that case -e is passed to babashka and babashka interprets -e foo as "execute the expression foo` which is why you see that message

and babashka doesn't have support for -- yet, but I did want to add that

@stijn Just made that issue yesterday: https://github.com/borkdude/babashka/issues/250

I see, makes sense

so you're dealing with two levels of argument parsing here, one for deps.clj and one for babashka itself

No worries, I can run with clj main for now. Really nice how you designed the usage of babashka with deps.edn, so you can easily switch between REPL on clojure JVM, main on JVM and babashka for running the shell scripts

thanks

Am I correct that babashka also executes the code when it is generating an uberscript?

(i mean, with deps.exe)

it shouldn't. it does run through the script for analysis, but it doesn't actually execute any functions

or maybe it is deps.exe that is executing the code

❯ deps.exe -M:main -Scommand "bb -cp {{classpath}} {{main-opts}} --uberscript my-script.clj"
nil

that nil is the list of command line args that the main of my script prints out

does that generate a script for you?

it does

but if I put my real code in, it doesn't, since there are (System/exit 1) statements in there because the command line args don't match what the actual script wants

❯ deps.exe -A:main -Scommand "bb -cp {{classpath}} {{main-opts}} --uberscript my-script.clj" this is a test
(this is a test)

(defn -main [& args]
  (println args))

ah... hmm, I see! I have an option in sci (the interpreter) called :dry-run which is what babashka uses to analyze all the code instead of executing it and then emits all the code that was loaded to the uberscript. but I only check the :dry-run option in a function call, not when doing interop... https://github.com/borkdude/sci/blob/398d15b8d940dd53fac17a263bbba35318ef5a0e/src/sci/impl/interpreter.cljc#L474

so a workaround for now might be to wrap System/exit in a function and that should do the trick

let me try with that main function

ah, that is executes the main function might be a regression

ah I see:

(cond
               (ifn? f) (fn-call ctx f (rest expr))
               (:dry-run ctx) nil
               :else
               (throw (new #?(:clj Exception :cljs js/Error)
                           (str "Cannot call " (pr-str f) " as a function."))))

the order is wrong there

I swapped it when doing optimizations. doh!

ok 🙂

let me provide you with a fix for testing. do you run linux or mac?

linux

@stijn I pushed a fix to master. Shortly there will be a link for a new linux binary in #babashka_circleci_builds

I now also added the -- option

@stijn this should be it: https://3916-201467090-gh.circle-artifacts.com/0/release/babashka-0.0.68-SNAPSHOT-linux-amd64.zip

that works, cool!

confirmed that the -- works as well

deps.exe -A:main -Scommand "bb -cp {{classpath}} {{main-opts}} -- $@"

thanks for testing

hmm @deleted-user weren't you also having issues with the uberscript? might be the same as the above?

don't remember when this was

aah same issue then

want to test with a new binary?

if so, linux or mac?

https://3926-201467090-gh.circle-artifacts.com/0/release/babashka-0.0.68-SNAPSHOT-macos-amd64.zip

sure, no hurry

ah good, thanks

I'll make a new release with these fixes

done: https://github.com/borkdude/babashka/releases/tag/v0.0.68

it just has two bugfixes and one new thing, I'll append it to the previous announcement

@deleted-user I noticed you were using spartan.test, if you haven't read it yet, clojure.test is now built in

np 🙂