--- "Mark A. Flacy" <[EMAIL PROTECTED]> wrote:
> >>>>> "Noel" == Noel Yap <[EMAIL PROTECTED]>
> writes:
> Noel>
> Noel> Also, search tools will be useless if this
> programmer were
> Noel> programming in Java since the class names
> would be as meaningless as
> Noel> the filenames. I suppose he then could start
> relying heavily on
> Noel> comments.
>
> There is no requirement for the source file name to
> be remotely related to
> the name of the class(es) contained within it.
>
> There *is* convention and it *does* make life easier
> when you do so, but it
> is *not* a requirement. jtags will work in either
> environment.
The following output suggests otherwise:
nyap:jpmpsdev@EQUINOX:~/proj/asdf> cat Asdf.java
public class Aoeu
{
public static void main(String[] args)
{
System.out.println("Yo");
}
}
nyap:jpmpsdev@EQUINOX:~/proj/asdf> javac -classpath .
Asdf.java
Asdf.java:1: class Aoeu is public, should be declared
in a file named Aoeu.java
public class Aoeu
^
1 error
Am I missing something here? Is there a flag to make
this error into a warning?
If there isn't, I think the "should" in the warning
should be changed to "must".
Noel
__________________________________________________
Do You Yahoo!?
Yahoo! Greetings - Send FREE e-cards for every occasion!
http://greetings.yahoo.com
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
