Should we clean up the stack trace?

2 views
Skip to first unread message

Johnny Jian

unread,
Feb 25, 2010, 8:08:50 AM2/25/10
to gmoc...@googlegroups.com
It is well known that the stack trace of groovy code is usually too long for reading. Should gmock clean up the stack trace before throwing the exception just as Grails does, by removing the lines of groovy runtime and some of the gmock internal code?

Johnny
2010-02-25
Reply all
Reply to author
Forward
0 new messages