This week's book giveaway is in the General Computing forum.
We're giving away four copies of Arduino in Action and have Martin Evans, Joshua Noble, and Jordan Hochenbaum on-line!
See this thread for details.
The moose likes Beginning Java and the fly likes Package visibility Big Moose Saloon
  Search | Java FAQ | Recent Topics
Register / Login


JavaRanch » Java Forums » Java » Beginning Java
Reply Bookmark "Package visibility" Watch "Package visibility" New topic
Author

Package visibility

Willie Toma
Ranch Hand

Joined: May 11, 2001
Posts: 78
I don't understand this answer? Here is the Q&A.
What happens when you attempt to compile and run these two files in the same directory?
//File P1.java
package MyPackage;
class P1{
void afancymethod(){
System.out.println("What a fancy method");
}
}
//File P2.java
public class P2 extends P1{
afancymethod();
}
1) Both compile and P2 outputs "What a fancy method" when run
2) Neither will compile
3) Both compile but P2 has an error at run time
4) P1 compiles cleanly but P2 has an error at compile time
Answer:
4) P1 compiles cleanly but P2 has an error at compile time
Even though P2 is in the same directory as P1, because P1 was declared with the package statement it is not visible from P2
Adrian Yan
Ranch Hand

Joined: Oct 02, 2000
Posts: 688
Actaully, it's quite simple.
To use a package, you need to import it. If you add import MyPackage in P2.java, then it's fine.
Remember, package != directory.
 
I agree. Here's the link: http://ej-technologies/jprofiler - if it wasn't for jprofiler, we would need to run our stuff on 16 servers instead of 3.
 
subject: Package visibility
 
Similar Threads
Marcus Green - Exam 2 - Question 9
Mock Exam Question
Packages
Reg. Packages
Q from Marcus Mock test 2