Public Class in a source file

[Eric Lidell]

Why should a public class be in a source file having the same name as it is having?
Is it because of Access specification?
[e-mail]

Nothing is impossible!

[Ernest Friedman-Hill]

It is just a requirement enforced by many Java
compilers (javac included) ; it's not part of the
language definition. It allows the compiler to find
classes that it may need to compile while it's in
the process of compiling another class.
[ July 14, 2003: Message edited by: Ernest Friedman-Hill ]

[Thomas Paul]

Ernest is correct. This has been part of the language going all the way back to Oak. It is supposed to simplify dynamic compiling. If you are using a class in your class and that class hasn't been compiled yet, the compiler may be able to figure out where to look for it based on the source name.

[Eric Lidell]

Hi Ernest and Thomas,
Thanx for the answers.
Simon

[Eric Lidell]

I thought a source(class) had to be compiled already for it to be refered or used by another
class/program.when will dynamic compiling be used?
can u pls give me any example code /scenario?

[Joel McNary]

Dynamic compiling is used by the compiler, not the JRE. If you write the following:
Test1.java

package test;
public class Test1{
    public static void main(String argv[]){
        Test2 = new Test2();
    }
}

Test2.java

package test;
public class Test2{
    //; no implementation
}

And then run "javac Test1.java", you will discover that the compiler compiled both Test1 and Test2 classes.

[Eric Lidell]

Thanks Joel.
Btw,What does your motto mean?

[Joel McNary]

Roughly translated, it reads:
"How much wood could a woodchuck chuck if a woodchuck could chuck wood?"

[Dirk Schreckmann]

I always thought it was the following.
"How much wood would a woodchuck chuck if a woodchuck could chuck wood?"