Hi Ron, Does this have any chance of running on Android at all? There is no "java agent" on Android's VM "Dalvik" so the byte code instrumentation would have to be plugged in elsewhere. Clojure on Android already involves byte code manipulation as JVM byte code generated by Clojure's compiler has to be passed through a second step called "Dex" to turn it into Dalvik byte code. Currently this is done by (a) AOT-compiling the Clojure application as much as possible and doing the Dex as part of your build process and (b) using custom class loader that instruments byte code generated at runtime through "eval".
If only application generated byte code has to be instrumented in order for Pulsar to work, then Pulsar's instrumentation could be plugged into the same places one step before the Dex step. However you can't reach byte code from system classes/the run time library this way. Does Pulsar need to instrument system classes/the runtime library to do its thing? Cheers -- hank On Saturday, July 20, 2013 1:49:55 AM UTC+10, pron wrote: > > Featuring: distributed actors, supervisors, fiber-blocking IO, and an > implementation of core.async. > Read the announcement > here<http://blog.paralleluniverse.co/post/55876031297/quasar-pulsar-0-2-0-distributed-actors-supervisors> > . > > Imagine running an entire Ring handler inside a go-block... > > -- -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to [email protected] Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to [email protected] 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
