On Wed, Jan 27, 2010 at 4:03 AM, Gabi <bugspy...@gmail.com> wrote: > This exception is the biggest time waster for me when working with > Clojure. It doesn't give you a hint of where the problem really is. > I strongly suggest to improve parse error messages to contain > meaningful info.
I just wrote a patch to LispReader that in many cases can produce an exception like: java.lang.Exception: EOF while reading, starting at line 7 (bad.clj:15) So while bad.clj:15 indicates the file name and the fact that line 15 is the last one of the file, "starting at line 7" points out the line where the unclosed grouping construct started. This might be useful. Rich, care for a bug and patch for this? --Chouser http://joyofclojure.com/ -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
