I think most Java programmers use Exceptions or logging instead of asserts. The philosophy is that your code should always be able to gracefully handle any "impossible" condition.
The great advantage of Exceptions is they can be caught and handled by your code, re-thrown with wrapper Exceptions, and they can propagate up the call chain. The downside is you need to code them intelligently. I won't go into all the details here, and a good Java book would do the topic better justice than I. Logging usually provides a better time-sequence context for exceptional conditions. Additional code quality tools are unit tests and a good IDE with debugger (I always get a kick out of debugging Java servlets with Eclipse). -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
