tags:

views:

133

answers:

3

I've been playing a bit with Clojure and so far is fairly impressed, but one thing that I keep running into is wierd error messages from Clojure. This comes in two forms: Java errors, like null pointer exceptions and in clojure syntax errors, like missing parenthesis pair. I was wondering if anyone know of a way to get better error messages?

Part of it is of course from learning a new language, but improving the error messages can never hurt :)

+3  A: 

Well, the compiler and other stuff are being developed by a fairly small band of people led by Rich Hickey, and if you're a competent programmer then it's conceivable you could contribute to the compiler's development.

Clojure headquarters is at: http://clojure.org

You can get information and documentation there, and access to the source code and git repository...

...and there's a Google Group for it: http://groups.google.com/group/clojure?pli=1

Take a look and offer your help, if you dare. Good luck and power to you!

Carl Smotricz
Yes the lack of good error messages is certainly something that should be taken up by the community.
dnolen
Yeah maybe simply reporting bugs for some cases would be a good start :-)
Anders Rune Jensen
A: 

I would just love a way to filter out the back-traces from the compilation process and see only the messages from the running of my program.

Arthur Ulfeldt
Different problem/question. But MUCH easier to fix! This would be a function of either your build script or IDE (whatever you're using). You can probably get a useful answer if you post the question here (as a new question!) with enough detail to reveal your environment.
Carl Smotricz
+1  A: 

This might help: http://github.com/mmcgrana/clj-stacktrace.

You can use it on the REPL to get more useful stack traces. It's still not great, but definitely better than nothing.

bm212