> OK, cool. That is another benefit of AOT compilation. The primary use > for :gen-class is when the Java side needs a class it can refer to > explicitly by name. For other cases, a good way for Java to > communicate with Clojure code is to use a proxy. On the Java side, you > can define an Interface and on the Clojure side you can define a proxy > that implements that interface by way of Clojure functions. There's a > runtime performance cost to doing that, but you gain the ability to, > for example, redefine any of the functions that implements the > Interface methods and have the change be effective immediately.
...How severe would the runtime cost be to invoke such functions? It's a shame about the lack of official support for java-side invocation- the bulk of my code is still implemented in java (largely for efficiency reasons), so it would be handy to be able to initiate things largely from that side. I *was* planning to write up some interfaces for more frequent/time-critical communications, but having to compile things via ant or the command line is a pain, and Eclipse doesn't have particularly good support for mix-and-match of java and clojure files in the same project (at least atm.) You can see some (but not much) info on the project here- http://forum.paradoxplaza.com/forum/showthread.php?t=410730 --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
