try{.....}catch

hello, this tut is about to stop server crashes and im gona tell you how
by using the try-catch methode an error can be turned into an message, also an crash will be turned into an message..

for example
your newvoid1 keeps crashing ur server

Code:

---

public void newvoid1()
{
callvoid2();
}

---

when u add the try and catch methode your server wont crash but simply prints and line...

Code:

---

public void newvoid1()
{
try{
callvoid2();
} catch (Exception e){
misc.println("error in newvoid1");
}
}

---

how to use?
at the start of an void u add:

Code:

---

try{

---

at the end above the last "}"
u add

Code:

---

catch (Exception e){
                misc.println("eror msg");
                }

---

This TuT is horrible in many ways. I bet you don't even know what it represents.

In my opinion this is pretty descent.

But why not make it even more great and add the destruct(); statement in the catch?

It's time for me to look into the destruct(); statement.

Umm, some things wrong with this:

1) Most people use Exception just in general, its better to use specific Exceptions (NullPointerException, IOException, InterruptedException just to name a few) for the try catch. Also, your forgot the optional "finally", like this:

try {
System.out.println(object);
} catch (NullPointerException) {
System.out.println("object is null!");
} finally {
System.out.println("object was not null!");
}

ok nice gratz

Quote:

---

Originally Posted by azn_sinz [Only registered and activated users can see links. Click Here To Register...]

It's time for me to look into the destruct(); statement.

---

It really just ends the running void when the error is detected.

Nice job, Its a start I suppose but needs some work.

Quote:

---

Originally Posted by Newb 2341 [Only registered and activated users can see links. Click Here To Register...]

It really just ends the running void when the error is detected.

---

I'm adding that to my brain =p.