On Tuesday, September 2, 2014 5:13:49 PM UTC-7, Beau Fabry wrote:
apologies, not a leiningen plugin. https://github.com/AvisoNovate/pretty
Thank you. This looks most interesting. I was able to find clj-pretty-error
on Clojars; github is https://github.com/liquidz/clj-pretty-error, but it
On Monday, September 1, 2014 7:24:54 PM UTC-4, Beau Fabry wrote:
The pretty-errors leiningen plugin might be worth a look
Hm... I don't see that particular plug-in in the [main lein plug-in
list](https://github.com/technomancy/leiningen/wiki/Plugins).
Do you mean
apologies, not a leiningen plugin. https://github.com/AvisoNovate/pretty
On Wednesday, September 3, 2014 2:17:21 AM UTC+10, John Gabriele wrote:
On Monday, September 1, 2014 7:24:54 PM UTC-4, Beau Fabry wrote:
The pretty-errors leiningen plugin might be worth a look
Hm... I don't see that
Where do you see a Java error here ?
I see the Clojure implementation
reporting that you are
trying to apply a numeric operator
to a null/nil value :)
I agree the JVM stack traces are not nice
and polluted by all the frames which
may/may not be relevant.
The messages are not always as clear as
On 01/09/2014 17:50, Luc Prefontaine wrote:
Where do you see a Java error here ?
I see the Clojure implementation
reporting that you are
trying to apply a numeric operator
to a null/nil value :)
I agree the JVM stack traces are not nice
and polluted by all the frames which
may/may not be
Ah ! Emacs, an old friend that I should eventually revisit after 30 years...
Long time no see :)
Luc P.
On 01/09/2014 17:50, Luc Prefontaine wrote:
Where do you see a Java error here ?
I see the Clojure implementation
reporting that you are
trying to apply a numeric operator
to a
The pretty-errors leiningen plugin might be worth a look
On Tuesday, September 2, 2014 7:58:31 AM UTC+10, g vim wrote:
On 01/09/2014 17:50, Luc Prefontaine wrote:
Where do you see a Java error here ?
I see the Clojure implementation
reporting that you are
trying to apply a
Looks like you figured this out, but sharing in case it helps others.
It turns out the JVM actually has a special caching mechanism for making
NullPointerExceptions fast (and near-impossible to debug):
http://stackoverflow.com/a/3010106
This link also has a JVM opt to stop this optimization,
