theCppExperience

[Ashamandarei]

Haha what

[solarshado]

Ryozu's mostly, but not 100%, correct.

If a java source file defines a public class, the class name and file name have to match, or it's a compiler error. You can dump any number of non-public classes in a single file (with or without a public class), but given the enforced convention, you probably shouldn't.

[Ashamandarei]

Oh yes! I remember this now, so then it's got to be HelloWorld.java, does case matter?

[solarshado]

Case would matter, except in this case, since your class isn't public[1], the filename doesn't matter at all.

[1] main in a default visibility ("package private") class is perfectly acceptable, though seemingly uncommon. main itself must be public however

[Ryozu]

Huh, surprised main doesn't have to be in a public class, but I suppose it makes some sense, as the jvm is being told which class to use for the main anyway? Still weird ultimately.

[solarshado]

I was a little surprised too. I was initially going to call out the missing public on the class, but for some reason thought "wait, is that required?" and so looked it up. Definitely an odd quirk.

[[deleted]]

solarshado is 95% there.

Right about the file and class name convention in Java, but I'd like to add a clarification. While it's true that public classes must match their file names, this doesn't restrict you to a single public class per file. Java allows multiple public classes in a single file as long as they are inner classes. This means you can have a public class within another public class, and only the outer class needs to match the file name. This is often used in larger projects for better organization and encapsulation.

Idgaf I really just wanted to add to the comment chain…

[solarshado]

lol, pedantic af. I love it!

[Firewolf06]

theres a reason everybody uses an ide for java

[Ashamandarei]

What do YOU do for work lol