Home >Java >javaTutorial >What are the naming rules for java identifiers

What are the naming rules for java identifiers

百草
百草Original
2024-01-10 10:14:271952browse

Naming rules for java identifiers: 1. Identifiers can be composed of letters, numbers, dollar signs, and underscores; 2. The first character of the identifier must be letters, dollar signs, or underscores; 3. Logo Identifiers cannot be Java keywords and reserved words; 5. Identifiers should be descriptive so that other developers can understand their purpose;

What are the naming rules for java identifiers

This tutorial operating system : Windows 10 system, DELL G3 computer.

The naming rules for Java identifiers are the rules used in the Java programming language to define the names of variables, classes, methods, constants, etc. The following is a detailed description of the naming rules for Java identifiers:

1. Identifiers can be composed of letters, numbers, dollar signs ($) and underscores (_).

2. The first character of the identifier must be a letter, dollar sign ($) or underscore (_).

3. Identifiers cannot be Java keywords or reserved words. For example, identifiers cannot be named if, for, while, etc.

4. Identifiers are case-sensitive, so myVariable and myvariable are two different identifiers.

5. Identifiers should be descriptive so that other developers can understand their purpose.

6. Usually, use camel case naming to name identifiers. This means that the first letter of the first word of the identifier is lowercase and the first letter of each subsequent word is uppercase. For example, myVariableName.

7. For class names, it is recommended to use camel case naming, that is, the first letter of each word is capitalized. For example, MyClass.

8. For constant names, it is recommended to use all uppercase letters and underscores to separate words. For example, MY_CONSTANT.

9. For method names, it is recommended to use camel case naming, that is, the first letter of the first word is lowercase, and the first letter of each subsequent word is capitalized. For example, myMethodName.

10. For variable names and method names, it is not recommended to use a single character as an identifier, except under certain special circumstances.

11. Avoid using Java reserved words as identifiers. For example, an identifier cannot be named int or void.

12. Avoid using negative numbers or identifier names with negative signs unless there are special reasons.

13. For identifier names with multiple words, it is recommended to use underscores (_) to separate words instead of using camel case nomenclature. For example, my_variable_name instead of myVariableName.

14. For constant names, it is recommended to use all uppercase letters and underscores (_) to separate words. For example, MY_CONSTANT_VALUE instead of myConstantValue.

15. For the attribute names in the Java Bean specification, it is recommended to use the camel case naming method, that is, the first letter of the first word is lowercase, and the first letter of each subsequent word is capitalized. For example, myProperty instead of my_property or MY_PROPERTY.

16. For package names, it is recommended to use lowercase letters and reverse domain names to name packages. For example, com.example.mypackage.

17. For enumeration constant names, it is recommended to use all uppercase letters and underscores (_) to separate words. For example, MY_ENUM_CONSTANT instead of MyEnumConstant.

The above is a detailed description of the naming rules of Java identifiers. Following these rules can help developers write understandable, maintainable, and extensible Java code.

The above is the detailed content of What are the naming rules for java identifiers. For more information, please follow other related articles on the PHP Chinese website!

Statement:
The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn