Reading Clojure Stacktraces

Clojure stacktraces are not incredibly user friendly. Once I got used to the status quo, I forgot how much noise lives within a stacktrace; however, every so often a Clojure beginner will remind the community that stacktraces are a bit convoluted. You can blame the JWM, lack of prioritization from the Clojure community, or someone else if you wish, but the reality is - I don't expect stacktraces to change anytime soon. This blog entry is about separating the signal from the noise within a stacktrace. note: all code for this blog entry can be found at: http://github.com/blog-jayfields-com/Reading-Clojure-Stacktraces Let's start with a very simple example. Running (I'm using 'lein run') the above code you should get a stacktrace that looks like the output below. lmp-jfields03:reading-clojure-stacktraces jfields$ lein run Exception in thread "main" java.lang.RuntimeException:...

Full article: http://blog.jayfields.com/2012/06/reading-clojure-stacktr...

Tweets

@wolfeidau » 30 Jun '12, 10pm
Interesting post on Clojure stack traces [link] cc @nicholasf
@ykomatsu0 » 29 Jun '12, 1pm
Clojureのスタックトレースはどうやって読めば良いのか、という話 [link]
@KageKirin » 27 Jun '12, 12am
Reading Clojure Stacktraces [link] via @zite
@rogier » 26 Jun '12, 1pm
RT @planetclojure: Reading Clojure Stacktraces [link]
@HornedKavu » 26 Jun '12, 12pm
RT @planetonrails: Reading Clojure Stacktraces [link]
@planetonrails » 26 Jun '12, 12pm
Reading Clojure Stacktraces [link]
@KCITP » 29 Jun '12, 6pm
Reading #Clojure Stacktraces [link]
@tsubame959 » 26 Jun '12, 4pm
RT @planetclojure: Reading Clojure Stacktraces [link]
@curious_corn » 26 Jun '12, 2pm
RT @planetclojure: Reading Clojure Stacktraces [link]
@planetclojure » 26 Jun '12, 1pm
Reading Clojure Stacktraces [link]