Oh, not when you don't have too. I mean, you can always hand write a class in Java and have it call into Clojure. That's effectively gen-class but done manually. Otherwise, I favour the Clojure Java API.
But some code base are already using gen-class, and some people do use gen-class. Sometimes it works and it's easier then having to write Java and modify your build to also use javac and include Java built artifacts. In those cases, the AOT is problematic, because it brings in dependencies, so if you package them as libraries, you get additional classes which can then conflict. So you need to find a way to only include the generated class and nothing else. -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/clojure/bf3a22ec-efd0-4508-8e41-895a1329e328%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
