[GregBrannon]

kahem42, on 10 July 2012 - 08:07 AM, said:

would someone allow me to send them all the project files and correct the errors would be very grateful

Haha! Good one.

[kahem42]

Its not Homework or anything its just a Time killer

[SwiftStriker00]

kahem42, on 10 July 2012 - 11:38 AM, said:

Its not Homework or anything its just a Time killer

Thats not the point. The point is *you* are supposed to be learning and trying to fix the code. We don't give solutions, we help and teach. We gave you a few to get you started. Half your errors are the same as the ones we already fixed. I also gave you a link to a tutorialon how to dissect these errors and easily fix them.

Make a serious attempt at fixing the code, then if you get stuck. Comeback explain where you are stuck and what you have tried. Then we will be happy to help.

[jon.kiparsky]

Yes, but it's your time you're killing. Not mine.

Fixes:
First, correct your indentation
Second, make sure your braces are matched
Third, review the syntax of constructions you're not clear on, like try/catch/finally, and repair those
Fourth... profit!

[kahem42]

1) i cant write java or c++ i can simply edit something of them and change things around i downloaded a source code and began to edit when it came to compiling i found errors in files i didn't change im not planing on making any money from this just to gain experience

[macosxnerd101]

Then perhaps you're doing too much. Pick a simpler project and write it from scratch. Look at intro classes for assignments. We're hear to help members with their problems, not with correcting code they copy/pasted. If you don't want to learn how to code, that's fine. Just don't expect others to correct things for you.

[jon.kiparsky]

If you want to gain experience, you'll get it by debugging your own code. You won't get it by watching someone else debug it for you, any more than you can learn to hit a target by watching someone practice archery.

Learn the syntax, fix your code so you can see where you're bollixing the syntax, fix the syntax.

At its simplest, a try/catch block looks something like this:

try {
  dangerousOperation();  // do something that might throw an exception
}
catch (UnmetExpectationException fse)   // catch a particular exception
{  // deal with the situation here
  logger.log("Operation failed: expected something, got something else.");
}

[kahem42]

can you only have one operation?

[macosxnerd101]

One operation for what?

[SwiftStriker00]

No, you can have as much code as you want in a try block. However if any of those operations throws an exception, it will stop and skip to the catch statement.

[jon.kiparsky]

As I said before, you should minimize the code in the try block. Try blocks are for special handling. The point is to catch a particular problem and deal with it, that's easiest when you minimize the contents of the try block and catch specific Exceptions.

There are no language-based limitations to the scope of a try block. This is legal, but not recommended:

public static void main(String[] args)
{
  try{
     JFrame frame = new JFrame();
     // put stuff in the frame  
     // turn the user loose on that stuff
     // get some data from the user
     // process the data - the problem you know about is here
     // write processed data to a file
     // exit
  }
  catch(Exception e)
  { 
     
     e.printStackTrace();
  }
  // exit the program
}

This can even work, as long as you, the programmer, are the one running it and can debug it.

If you expect the program to be used by anyone else, you're dropping your failures in their lap, and that's bad programming.