Thread: throwing and returning

Throwing interrupts normal program flow. I guess in a sense it does act like a return statement, but like literallyjer said, it's looking for something to catch the exception it threw (well, technically there are other things that can be thrown, but for the most part it'll be exceptions).

public void doIt1(Boolean something)
{
    if (something)
    {
        throw new NullPointerException();
     }
     System.out.println("doIt1: this will never get executed");
}
 
public void doIt2()
{
     doIt1(true);
     System.out.println("doIt2: this well never get executed");
}
 
public void doIt3()
{
    try
     {
          doIt2();
          System.out.println("doIt3: no exception was thrown");
     }
     catch(NullPointerException e)
     {
          System.out.println("doIt3: caught a NullPointer Exception");
     }
}

The performance difference is almost negligible This really only applies when you're throwing a ton of exceptions, then maybe you would want to look into other ways to structure your code.