2009-10-01, 01:39 AM
Well, I really only use try/catch for Java when it forces me to. For example, whenever I'm using IO shyts. I didn't really tell the code to do anything other than error.printStackTrace(); if it turns out an IOException, which to me says "very serious problem with ur hardwarez", and the only one where I have extensive "else" stuff for error catching is when for whatever reason an image file with an illegal name was attempted to be written.
But yeah, other than dealing with IO, I almost never do try/catch stuff since I'm wary of crazy crap happening in the realm of errors. Funny stuff already happens with me running flash games (rebooting FF usually resolves them), I don't need to see more mystery errors.
But yeah, other than dealing with IO, I almost never do try/catch stuff since I'm wary of crazy crap happening in the realm of errors. Funny stuff already happens with me running flash games (rebooting FF usually resolves them), I don't need to see more mystery errors.

