Counterclockwise broken?
Aug. 11th, 2012 05:01 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
izardJust upgraded counterclockwise (clojure plugin for eclipse), and faced a problem:
With older version I was able to run a clojure app from REPL, and keep using REPL to experiment with app's state while it was running. Not with latest counterclockwise. Now REPL is useless until app finishes or I kill it.
There should be a workaround (to start-off app asynchronously) and I am certain I will find it. I just don't understand the motivation behind the change, it defies the most beautiful feature of REPL: ability to experiment with a live system.
Upd: After 10 minutes thinking it is obvious that I should now just type
REPL> (future -main)
instead of
REPL> (-main)
All works as expected. Still no idea why the default behavior was changed.
With older version I was able to run a clojure app from REPL, and keep using REPL to experiment with app's state while it was running. Not with latest counterclockwise. Now REPL is useless until app finishes or I kill it.
There should be a workaround (to start-off app asynchronously) and I am certain I will find it. I just don't understand the motivation behind the change, it defies the most beautiful feature of REPL: ability to experiment with a live system.
Upd: After 10 minutes thinking it is obvious that I should now just type
REPL> (future -main)
instead of
REPL> (-main)
All works as expected. Still no idea why the default behavior was changed.
