Jump to content

Recommended Posts

Posted

This tutorial is meant to serve as a basic introduction to handling errors and exceptions in Java using such techniques as try-catch blocks and assertions. Before tackling this tutorial, you should have a firm grasp on the basic concepts of Java. Please enjoy the tutorial.

 

Most of us have dealt with the problem of errors or exceptions at some point in our programming experience. Enter the wrong data type, or even data that is unexpected such as a number that is to big, and your whole program crashes. However, there are some simple techniques that you can use to "catch" that unexpected data and deal with it in a more organized manor than your program outputting some incomprehensible error message.

 

Lets say you have a piece of code that sums up some numbers, for example:

//Some code
double sum = 0;
for(int i = 0; i < arguments.length; i++) //for every argument, add it
sum += arguments[i];
System.out.println(sum);
//Some code

 

This is pretty straight forward. In this code fragment, you take some numbers as arguments to the program and total the sum of the numbers using a for loop. This works fine if all the input consists of is numbers. But lets say one of your users decides they're going to get mischievous on you and input a character like so:

SumNumbers 0 5 2 5 x

Now your program exits with some odd error message that scares your user half-to-death (this is an exaggeration, it probably won't scare them that much). There is a simple solution to this problem. All we have to do is modify the code like so:

//Some code
double sum = 0;
for(int i = 0; i < arguments.length; i++)
{
try
{
	sum += arguments[i];
} catch (NumberFormatException e)
{
	System.out.println("Non-number input: " + argument[i]);
}
}
System.out.println(sum);
//Some code

What we did here is add in something called a "try-catch" block. Try-catch blocks allow your program to catch errors and handle them in a way that you specify. You can use try-catch blocks for a number of more complex purposes than the one shown in this program. For example, maybe instead of just outputting the error you might want to convert the string to a number. Or even ask the user to input the correct number in place of your current number.

 

Try-catch blocks can also be used to catch multiple errors by simply using different catch blocks for every type of exception you want to handle. This is done like so:

try
{
//Some code to try
} catch (NumberFormatException e)
{
//Handle number format exceptions
} catch (ArithmaticException e)
{
//Handle arithmetic exceptions
}

This way, you can handle pretty much any type of error that your encounter. Also, a word about exception types. There are many different types of exception types specified by Java. All have different cases in which they are used. If you want to handle any exception with a generic response, however, simply use a block like this:

try

{
//Some code
} catch (Exception e)
{
//Catch any exception
}

All exceptions inherit from the exception class, so this statement will catch any exception. There is one more thing that you can do in try-catch blocks called a finally statement. Finally statements execute no matter what and are placed at the end of your try-catch block. For instance, here is a generic try-catch-finally block:

try
{
//Try some code here
} catch (Exception e)
{
//Catch any exceptions here
} finally
{
//Do this statement no matter what
}

There is another weapon available to Java developers in the eternal battle against errors and exceptions. The "assert" statement allows programmers to setup a checkpoint in their software to make sure their variables are on track and have the right value. Assert statements are basically Boolean if statements that allow you to check a condition and output an error message if it is not true.

 

For example, lets say you just wrote some software to maintain inner workings of a nuclear energy plant. It might be a good idea to let the folks working there know if the temperature gets to hot so they can have a little time to evacuate before it explodes huh? Well, the assert statment makes this easy. Take a look at the following code.

//Code that manages the power plant
assert temperature <= 4000 : "She's gonna blow! Run for the hills!";

This statement just checks to make sure that the temperature is at or below 4000 and if it isn't, it outputs a friendly error message to the workers.

 

This tutorial should serve as a basic introduction to some techniques for handling errors and exceptions in programs. It is by no means a comprehensive guide for handling errors, but shows some basic techniques that can be easily implemented in any program.

Credits: whitey6993

Posted

Good share, but maybe You can try to create something by your self now?

 

Anyway, add proper prefix, [Guide] in this case.

 

Thanx.

  • 3 weeks later...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


  • Posts

    • Thank you very much. It would also be good if you looked into this issue. UnknownSoldier has been manipulating me to make me look bad. He deleted all the evidence I uploaded and left all the insults against me. You'll also see that on April 26th, he reopened the thread and then locked it again just so his friend from Argentina could post: links down :l XD   In the thread: https://maxcheaters.com/topic/253997-sourceservercliente-l2devs-files-l2devscom/page/2/ They do this so they can later tell people that I deleted the links because it was a lie, and so on. Realize that all the damage you're causing is related to this same person. Regards and thank you very much! 🙂 PS: I would like UnknownSoldier to publish the evidence for why he has repeatedly called me a SCAMMER and explain why he also says that to other people. This person is using forum privileges to smear and discredit those who don't work with him. I WANT ALL THE EVIDENCE OF WHAT HE'S SAYING.  
    • Theres a lot of drama going on about Guytis scamming people. I want real, solid proof showing that he scammed anyone attach everything you have.   About reputation: we’re all adults here, yet some are acting like kids fighting over pixels. Think before spreading rumors. False claims don’t make you look better they make you look worse.   I’m waiting for actual evidence that he scammed any user. If there’s nothing to back it up, I’ll deal with it myself. Time’s running out this has been going on long enough.
    • I’ve read the whole topic about Baylee and Protojah. From what I can see, Baylee wanted to buy some htmls and they agreed on a price. Later, Baylee changed her mind and decided not to go through with it. The product wasn’t delivered because Baylee changed her mind. Even if she initially agreed to the price, to avoid confusion. if the files had been sent and payment not made, I would call it a scam. But since they weren’t sent, this isn’t a scam.   I want to stress that I try to be fair to everyone, no matter the situation.   Yeah, Protojah did put in time and effort, and that’s fine, but disagreements happen all the time, even in real life jobs, no matter what the work is. I’m going to lock this topic to avoid more drama. Please keep all personal issues in private messages. And before anyone says anything else I’m not taking sides. I don’t protect scammers and I ban them, but since this isn’t a scam, you both should resolve this situation in DMs.
  • Topics

×
×
  • Create New...

Important Information

This community uses essential cookies to function properly. Non-essential cookies and third-party services are used only with your consent. Read our Privacy Policy and We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue..