It's odd to me that that the stack traces were only removed in a few
instances. There are still plenty of places that do print traces.

I'm all in favor of getting rid of the "meaningless" stack traces,
once we have better error reporting.

Allen

On Oct 11, 2:36 pm, Chouser <[EMAIL PROTECTED]> wrote:
> On Sat, Oct 11, 2008 at 1:26 PM, Allen Rohner <[EMAIL PROTECTED]> wrote:
>
> > If you exercise the bug in my previous post about resultset-seq, the
> > repl will not print a stack trace, it will only print the name of the
> > exception and the message.
>
> That's a feature!  I recent one, no less.
>
> Seriously, people were complaining about giant "meaningless" stack
> traces at the REPL, so the default now is to just print the exception
> itself.  To get the stack trace after an exception has occurred, try:
>
> (.printStackTrace *e)
>
> --Chouser
--~--~---------~--~----~------------~-------~--~----~
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
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/clojure?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to