Brian Marick writes:
> I've also noticed that the messages that come from botched
> macroexpansions are often not useful in that they contain no clues
> about the original source, and sometimes not even a useful reference
> to the original namespace.
If these are macros that are under your contr
I've also noticed that the messages that come from botched macroexpansions are
often not useful in that they contain no clues about the original source, and
sometimes not even a useful reference to the original namespace.
I have a similar problem in Midje. When a macroexpansion blows up, I catch
A typo in an identifier should not lead to the following. Although I understand
that `lein repl` trims stack traces, that should be the default, rather than
having every substantial user-facing program trim `clojure.lang.Compiler`
(etc.) messages for the sake of its users.
> Exception in threa
On Friday, January 25, 2013 6:27:48 AM UTC+11, Michael Klishin wrote:
[..]
> Because poor error messages primarily trip newcomers to the language,
> I am a bit surprised to see this issue discussed on the closed
> mailing list said beginners cannot join [quickly or at all].
>
> So, if you have so
Here are some more: (which I'm getting from my old gist from here
https://gist.github.com/3895312 after I recheck those and tell you only the
ones relevant to this subject)
1. This one has to do with namespace expected format for :import
https://groups.google.com/d/msg/clojure/JCwpbqbrHUE/m1Fx13Ye
repl-y (Lein's default repl) only shows the first line of the stack trace
rather than the whole thing. nrepl.el can optionally behave the same.
It's a good default - as I see it, it relieves 90% of the pain associated
to errors in clojure.
As for the contents of those first-lines - it often is
On Jan 24, 2013, at 11:27, Michael Klishin wrote:
> So, if you have something specific to say on the topic, say it here.
Well, these comments more general in nature; hope that's OK...
I find Clojure's default error messages to be noisy, ugly, and hard to
decipher. What I'd like is a short, clear
Hi.
There are a bunch of calls to Util.runtimeException("msgHere") which can be
replaced with Util.runtimeException("msgHere", e); where e is the exception
just caught (aka the cause), for example here:
https://github.com/clojure/clojure/blob/master/src/jvm/clojure/lang/Compiler.java#L4570
and her
