5 ms·

When something blows, arent you just happy to get as much information as possible? I remember when developing in VB classic, youd get something lile "error -68

• antoineMoPa 10y ago
  I prefer something in between. Something like: the method that called the current method, the line number and a sentence describing the exception. No need to know the function-that-called-the-function-that-called-the-fun[...]
  • Sharlin 10y ago
    In my experience the direct caller usually tells me very little about the root cause of the exception. The interesting context is often at least ten frames separate from the proximate cause in even moderately complex Java programs. Of course, often there's an additional couple dozen lines in the trace that aren't very useful...
  • deleted 10y ago
    [deleted]
  • frugalmail 10y ago
    That's sounds like you work on very small projects. That function-that-called-the-function-that-called-the-fun could behave very differently through that path due to calling parameters, environment or data issues.
• CSDude 10y ago
  The level of verbosity is good, however when you replace almost all your catch exceptions with ex.printStacktraces() it gets enormously large and unmaintainable across a large project when too many things prints stack taces concurrently. Not the way I like to do it, however too many people do that unfortunetaly: http://plg.uwaterloo.ca/~migod/846/current/projects/09-NakshatriHegdeThandra-report.pdf http://plg.uwaterloo.ca/~migod/846/current/projects/09-Naksh...
  • deleted 10y ago
    [deleted]
  • frugalmail 10y ago
    That's a problem on the other side of the keyboard.