Can't Access Variables that are inside a try block

Thanks for your help.

Can I declare the variable outside the try block, manipulate it inside the try block, and use it outside the try block? (Say it goes in equal to 1, inside the try block it becomes equal to 2, when I use it again outside the try block will it be equal to 2?)

Message was edited by:

louy

louya at 2007-7-15 2:45:20 >

I tried that and it is still not working. Maybe my problem is different from what I thought it was originally. This is what is going on: I am parsing a string to an integer. The string is defined inside the try block (it has to be because it is coming from an external file), then I parse the string outside the try block, but it doesn't recognize the original string variable i am trying to parse.

variable strheightRows might not have been initialized

int heightRows = Integer.parseInt(strheightRows);

If I try to get around that and parse the string inside the try block, the program doesn't recognize the newly created integer variable, so I am stuck.

Message was edited by:

louy

louya at 2007-7-15 2:45:20 >

Here are my variable declarations & then my try block:

String inputLine, line1, line2, line3;

String strwidthCols, strheightRows, strexitRowCoor, strexitColCoor, strenterRowCoor, strenterColCoor;

try

{

BufferedReader input = new BufferedReader(new FileReader("MazeInstructions.txt"));

try

{

line1 = input.readLine();

StringTokenizer st1 = new StringTokenizer(line1, "");

strwidthCols = st1.nextToken();

strheightRows = st1.nextToken();

}

catch (IOException z)

{

System.out.println(z);

System.exit(1);

}

}

catch (FileNotFoundException e)

{

System.out.println(e);

System.exit(1);

}

Here is what I am trying to do outside the try block:

int heightRows = Integer.parseInt(strheightRows);

((I removed some unnecessary code)

Message was edited by:

louy

louya at 2007-7-15 2:45:20 >

If you want a quick hack you could try this.

int heightRows = 0;

if(strheightRows != null) {

heightRows = Integer.parseInt(strheightRows);

}

floundera at 2007-7-15 2:45:20 >

> > Rather then System.exit(), you should either not

> > catch the exception at all, or wrap it and rethrow

> it.

>

> From what I can tell, I have to try/catch it or the

> compiler spits out an error -

Not if you declare your method to throw it.

Catching it and then doing nothing just to make the compiler happy defeats the purpose of exceptions. The whole idea is that if something goes wrong that your method can't fix, the calling method knows about it.

jverda at 2007-7-15 2:45:20 >