@Billy, thnks for adding your implementation and you are absolutely correct. That makes it 4 different ways to use the try/catch blocks. Nice, we should pin this up somewhere for a quick reference in the future for the community use. Note that I did not even mention about Googling for inputs to this thread because if we understand the concepts, we can create more powerful features that are user friendly. For example, using other exception handlers, you can catch DNS and TCP errors to a certain level. If implemented correctly, assume that the end user launched the program and forgot to connect their internet connection, the result would be more user friendly than just having a blank page which stares at the user. Great stuff. :-) On Fri, Nov 25, 2011 at 11:20 AM, Billy <billyx5@gmail.com> wrote:
@Aki, @Daniel First, it is not good practice to only catch the generic "Exception" - you should catch a specific Exception THEN catch Exception at the end And the kind of nesting you use depends on whether you can handle the exception and allow execution to proceed or not