Re: intuitive stack trace

2010-03-30 Thread Stuart Sierra
On Mar 29, 2:23 pm, strattonbrazil strattonbra...@gmail.com wrote: I do something wrong, I have to read through the stack which sometimes just says there's an error at line 0, which doesn't help me much. One problem is that the compiler can't keep track of line numbers in the REPL (or SLIME).

Re: intuitive stack trace

2010-03-30 Thread Rick Moynihan
On 30 March 2010 14:37, Stuart Sierra the.stuart.sie...@gmail.com wrote: On Mar 29, 2:23 pm, strattonbrazil strattonbra...@gmail.com wrote: I do something wrong, I have to read through the stack which sometimes just says there's an error at line 0, which doesn't help me much. One problem is

intuitive stack trace

2010-03-29 Thread strattonbrazil
In the relatively short time of using clojure, I'm a little frustrated with it's limited information the stack provides. I'm assuming there's something I just don't know or am not doing. Many times when I do something wrong, I have to read through the stack which sometimes just says there's an

Re: intuitive stack trace

2010-03-29 Thread Meikel Brandmeyer
Hi, On Mon, Mar 29, 2010 at 11:23:29AM -0700, strattonbrazil wrote: (import '(javax.swing JTable) '(javax.swing.table TableModel)) (def table (new JTable((proxy [TableModel] [] (getColumnCount [] 10) (getRowCount [] 10)

Re: intuitive stack trace

2010-03-29 Thread Stuart Halloway
One nice thing about Clojure is that double-parenthesized ((anything)) is usually wrong. Stu Hi, On Mon, Mar 29, 2010 at 11:23:29AM -0700, strattonbrazil wrote: (import '(javax.swing JTable) '(javax.swing.table TableModel)) (def table (new JTable((proxy [TableModel] []

Re: intuitive stack trace

2010-03-29 Thread Mark J. Reed
But that doesn't address the fundamental lack of useful information in the error messages, which is something I've noticed as well. The compiler could stand to be a bit friendlier in this regard.. On Mon, Mar 29, 2010 at 3:55 PM, Stuart Halloway stuart.hallo...@gmail.com wrote: One nice thing

Re: intuitive stack trace

2010-03-29 Thread Stuart Halloway
Error messages could certainly be better, and please call my attention to any patches to this effect that have not gotten their due attention. The particular error message in question here comes from Java, and is more informative on more recent versions of Java. I get: