Currently CanJaguar Exceptions from WPILibJ are not handled, and all we get are
crappy stack traces. We need to propagate these through the API up to user
land. The challenge here is that while we have exception types, we want to
ensure backwards compatibility without violating java paradigms.
Time to stop sidestepping this issue.
Original issue reported on code.google.com by sparta...@gmail.com on 31 Mar 2011 at 5:42
Original issue reported on code.google.com by
sparta...@gmail.com
on 31 Mar 2011 at 5:42