The public type Test1 must be defined in its own file

This error message usually occurs when you have defined a public class or interface in a Java file whose name does not match the class/interface name. To fix this error, you can do one of the following:

1. Rename the Java file to match the public class/interface name.
2. Move the public class/interface to a new Java file with the correct name.
3. Make the class/interface package-private (remove the "public" modifier) if it does not need to be accessed from outside its package.

Here's an example:

// file name: MyClass.java
public class Test1 {
// ...
}

In this case, the file name should be renamed to Test1.java to match the public class name.

相关问题

The public type singleTon must be defined in its own file

This statement is not entirely true. While it is true that it is a common practice to define a singleton class in its own file, it is not a requirement or a rule that must be followed.

A singleton class is a class that can have only one instance, and it is often used in scenarios where you want to ensure that there is only one instance of a class in the entire application.

The implementation of a singleton class can vary depending on the programming language and the specific requirements of the application. In some cases, it may make sense to define the singleton class in the same file as other related classes or in a file that contains utility classes.

However, it is important to note that defining a singleton class in its own file can help to improve the clarity and organization of the code. It can also make it easier to maintain and modify the singleton class in the future.

The public type Square must be defined in its own file

This error message means that you have defined a public class called "Square" in a file where other classes are also defined. To resolve this error, move the definition of the "Square" class into its own file, separate from the other classes.

Here's an example of what the file structure might look like:

- Square.java (contains the definition of the public class "Square")
- OtherClass1.java (contains the definition of another class)
- OtherClass2.java (contains the definition of another class)

By separating the definition of the "Square" class into its own file, you can ensure that it is properly encapsulated and can be easily reused in other parts of your code.