The Weird and The Wonderful

aspdotnetdev wrote:

and a code horror

doja93 wrote:

graduating with a CS degree - at that point you should understand exceptions, scope and all sorts of fundamentals

doja93 wrote:

I recognize that it is technically harmless

try 
{
    // code that may throw exception here
}
catch(Exception ex) 
{
    // error logging here
    // re-throw the exception, the stack stays safe.
    throw;
}

try 
{
    // code that may throw exception here
}
catch(Exception ex) 
{
    // error logging here
    // re-package the exception then throw it 
    // probably losing the stack along the way
    throw ex;
}

function1()
{
try
{
calling function2()
}
catch(exception e)
{
//I handled the exception thrown from the functions/subs called
}

}

function2()
{
//if any error/exception comes here .net handler automatically throws it to the calling function/sub where it was handled.
}

mohan5k wrote:

I do not really understand why we have to catch the exception and throw it.

try
{
   // code that may throw exception here 
}
catch(SQLException sqlex)
{
   //Handle this exception here 
   //Don't re-throw the exception.
   //Other exceptions will remain uncaught.
}

try
{
   // code that may throw exception here 
}
catch(SQLException sqlex)
{
   //We really want to rethrow just that exception for some reason.
   throw;
}
catch
{
   //Whereas for everything else, we want to handle the exception here...
}

Rod Kemp wrote:

try {
// code that may throw exception here
}
catch(SQLException sqlex)
{
//Handle this exception here
//Don't re-throw the exception
}
catch {
throw; //re-throw all other exceptions that may occur
}

public int FormatSomethingOrRather(string txt)
{
   try 
   {
      // Convert string to int
   }
   catch (Exception)
   {
      
   }
}

doja93 wrote:

she, "..wanted to add exception handling.." to her code