Solved

Java: Scopping rules

Posted on 2009-05-15
7
205 Views
Last Modified: 2013-12-29
This is a question about scopping rules.   In the code sample I have purposfully done somthing goofy to as a test.  I expected that line 3, {int b = 3; int c = 4;} ,would result in redefinition of b and c and shadow the variables with the same names in line 2.  Instead it results in the compiler errors shown below.  My question is why is it that the inner scope of line 3 does not allow the variables in line 2 to be redefined?
------------------------------
src\Initializer.java:5: b is already defined in main(java.lang.String[])
                { int b = 3; int c = 4;}
                      ^
src\Initializer.java:5: c is already defined in main(java.lang.String[])
                { int b = 3; int c = 4;}
----------------------------
                                 ^
class Initializer{
 
	public static void main(String [] args){
		int b = 1, c = 2;
		{ int b = 3; int c = 4;}
		System.out.println("Initializer: " + b + " " + c);
	
	}
}

Open in new window

0
Comment
Question by:ssackett
  • 2
  • 2
  • 2
  • +1
7 Comments
 
LVL 3

Expert Comment

by:emce
ID: 24399481
the {...} by itself doesn't produce a new visibility scope
0
 
LVL 7

Expert Comment

by:zwei
ID: 24399598
emce is right.

For what you want to do you'd have to do something like this:
class Initializer{
        static int b = 1;
        static int c = 2;
 
        public static void main(String [] args){
                int b = 3;
                int c = 4;
                System.out.println("Initializer: " + b + " " + c);
        
        }
}

Open in new window

0
 

Author Comment

by:ssackett
ID: 24399788
emce & Zwei,

Why does the attached code fail to compile?  It seems that the b and c declared inside the initializer can't be seen outside the block (what I would expect) but that the block doesn't behave like a nested scope in other ways.
...
  {int b = 2;}
  b = 1
...

Open in new window

0
Netscaler Common Configuration How To guides

If you use NetScaler you will want to see these guides. The NetScaler How To Guides show administrators how to get NetScaler up and configured by providing instructions for common scenarios and some not so common ones.

 
LVL 17

Expert Comment

by:Thomas4019
ID: 24399921
The point of a custom block decaration { }, is so that variables declared inside can be garbage collected and deleted outside of the block
0
 
LVL 7

Expert Comment

by:zwei
ID: 24400021
The variables are both local variables and are both on the same memory stack within a single method. When you create a new scope, you move on top of the original stack, which is why you can't create a new variable with the same name:
int a = 2;
{int a = 3;} <-- illegal, a is still on the stack.

But when you create a variable within a new scope, when you leave that scope the variable dies which is why this works:

{int b = 2;} <-- b dies here
int  b = 1;
0
 
LVL 17

Accepted Solution

by:
Thomas4019 earned 125 total points
ID: 24400062
According to this link,

http://java.sun.com/docs/books/jls/second_edition/html/statements.doc.html

Java throws a compile time error because such naming can lead to very obscure and hard to detect errors.
0
 

Author Closing Comment

by:ssackett
ID: 31582049
Thanks for the help guys.  Yet another reason why it's dangerous to mix C and Java.
0

Featured Post

ScreenConnect 6.0 Free Trial

Want empowering updates? You're in the right place! Discover new features in ScreenConnect 6.0, based on partner feedback, to keep you business operating smoothly and optimally (the way it should be). Explore all of the extras and enhancements for yourself!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

After being asked a question last year, I went into one of my moods where I did some research and code just for the fun and learning of it all.  Subsequently, from this journey, I put together this article on "Range Searching Using Visual Basic.NET …
Java had always been an easily readable and understandable language.  Some relatively recent changes in the language seem to be changing this pretty fast, and anyone that had not seen any Java code for the last 5 years will possibly have issues unde…
Viewers learn about the third conditional statement “else if” and use it in an example program. Then additional information about conditional statements is provided, covering the topic thoroughly. Viewers learn about the third conditional statement …
Viewers will learn about the regular for loop in Java and how to use it. Definition: Break the for loop down into 3 parts: Syntax when using for loops: Example using a for loop:

770 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question