2011/3/31 Armando Blancas <armando_blan...@yahoo.com> > > So, really, all the current ccw behaviour wrt auto-compile, in background > or > > not, concept of "Clojure Application" will be reworked. > > One thing that ccw handles with ease is compiling Java for use right > there in Clojure. With auto-compile one could do the opposite just as > easy for dependent projects. I noticed that the OP had the right > instincts since that's how it works in Java. > > Maybe there could be a second run config for AOT apps. Where there's a > conflict it won't be too bad having to wait for the compiler to > finish. >
Oh I was more thinking of the fact that if the aot-compiled gen-class is already loaded from file, it won't be reloaded again during the same user-launched app anyway, and that it seems to also cause problems with java configs with the deletion of the file. Because AOT compiled gen-classes always have the same name, when recompiled files are always new files added in the package repository. -- 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
