登录查看更多内容

How do you choose the right access modifier for your class attributes and methods?

由人工智能和领英社区提供技术支持

Access modifiers are keywords that determine how other classes can access the attributes and methods of a class. They are an essential part of object oriented design, as they help to enforce the principles of encapsulation, abstraction, and inheritance. In this article, you will learn how to choose the right access modifier for your class attributes and methods, depending on the level of visibility and control you want to achieve.

此文章中的业界达人

由社区从 2 条内容中精选。了解更多

Paulo Z?mek

Software Engineer - I used talk to computers and they understood me even without AI, we just spoke the same language...…

1 Public access modifier

The public access modifier means that the attribute or method can be accessed by any other class, regardless of the package or hierarchy. This is the most open and flexible option, but also the most risky, as it exposes your class to potential misuse or modification by other classes. You should use the public access modifier only when you want to make your attribute or method part of the public interface of your class, and when you are confident that it will not compromise the integrity or functionality of your class.

添加您的观点

2 Private access modifier

The private access modifier means that the attribute or method can only be accessed by the same class, and not by any other class, even if they are in the same package or inherit from the same class. This is the most restrictive and secure option, as it hides your attribute or method from the outside world, and prevents any unwanted interference or dependency. You should use the private access modifier when you want to make your attribute or method an implementation detail of your class, and when you want to protect it from being overridden or modified by subclasses or other classes.

添加您的观点

3 Protected access modifier

The protected access modifier means that the attribute or method can be accessed by the same class, and by any subclass that inherits from it, regardless of the package. This is a middle ground between public and private, as it allows you to share your attribute or method with your subclasses, but not with other unrelated classes. You should use the protected access modifier when you want to make your attribute or method part of the protected interface of your class, and when you want to enable or encourage inheritance and polymorphism.

添加您的观点

4 Default access modifier

The default access modifier means that the attribute or method can be accessed by any class in the same package, but not by any class outside the package. This is also known as package-private or friendly access. This is a useful option when you want to limit the visibility and access of your attribute or method to a specific group of classes that belong to the same module or component. You should use the default access modifier when you want to make your attribute or method part of the internal interface of your class, and when you want to avoid exposing it to other packages or subclasses.

添加您的观点

Paulo Z?mek

Software Engineer - I used talk to computers and they understood me even without AI, we just spoke the same language... now that they got smarter we are so in-sync that sometimes it feels we talk to each-other mentally!
举报内容
The "default" access modifier is specific to Java. The default in C++ is private for classes, public for structs. C# has a similar modifier, internal, but it is not the default inside classes and structs, it is just the default inside namespaces. I think the article should explain that it is tied to java, or just explain that there are other modifiers depending on the language used.

已翻译

赞

5 Choosing the right access modifier

Choosing the right access modifier for your class attributes and methods depends on several factors, such as the purpose, functionality, and design of your class, the relationship and communication between your class and other classes, and the level of abstraction and encapsulation you want to achieve. As a general rule, you should follow the principle of least privilege, which means that you should grant the minimum level of access that is necessary for your class to work properly, and no more. This way, you can reduce the complexity, coupling, and vulnerability of your class, and increase its cohesion, modularity, and maintainability.

添加您的观点

Paulo Z?mek

Software Engineer - I used talk to computers and they understood me even without AI, we just spoke the same language... now that they got smarter we are so in-sync that sometimes it feels we talk to each-other mentally!
(已编辑)
举报内容
It would be nice to have examples for all the access modifiers, with an explanation of why they were used. For example, show a readonly class that sets all the values on the constructor, has a private field and a public getter. This covers both private and public. Then, another example that explores protected and default... or anything similar.

已翻译

赞

6 Here’s what else to consider

This is a space to share examples, stories, or insights that don’t fit into any of the previous sections. What else would you like to add?

添加您的观点

Object Oriented Design

+ 关注

给文章评分

我们借助人工智能创建了此文章。您认为这篇文章怎么样？

很棒不太好

举报此文章

查看全部

How do you choose the right access modifier for your class attributes and methods?

1

2

3

4

5

6

1 Public access modifier

2 Private access modifier

3 Protected access modifier

4 Default access modifier

5 Choosing the right access modifier

6 Here’s what else to consider

Object Oriented Design

给文章评分

感谢您的反馈

更多Object Oriented Design相关文章

更多相关阅读内容