CODEWITHSUNDEEP
oopencapsulationaccess-modifiers
Hexo
Hexo

Reputation: 215

Who do we protect our classes from?

I'm currently learning C# and I was wondering, what is the point of declaring classes / methods private? Who are we hiding / limiting access to these classes.

Because if someone was editing the source they could just change the tag from private to public. I'm not sure how a user will be able to access these methods and what problems it would cause.

tldr; What's the point of access modifiers.

Upvotes: 6

Views: 170

Answers (6)

Kevin Ji
Kevin Ji

Reputation: 10499

Access modifiers are used for encapsulation, so that the internals of an object/class are hidden from outside users or classes. This prevents users from accidentally or intentionally breaking an object/class by modifying its instance variables and/or functions.

Encapsulation is an important part of the Open/closed principle, which refers to a class being "open for extension" but "closed for modification". This principle allows the extension of classes without fear that the API of an class may change in the future.

Upvotes: 0

Bogdan T.
Bogdan T.

Reputation: 668

You can write code in 2 ways: designed for extension and designed for usage as it is.

You may or may not have access to source code.

Access modifiers are most important in code designed for extension where the client programmer (the programmer which extends and uses your code) needs to have access only to the API you expose - basically, to the interface you offer by using these access modifiers.

Upvotes: 0

Blorgbeard
Blorgbeard

Reputation: 103507

It keeps your code tidy. You separate your code into a public interface, and private internals.

That way, you can change your internals without fear of breaking code that depends on your class. You can also safely assume that no other code has modified your internal state while you weren't looking.

Upvotes: 1

Cody Bonney
Cody Bonney

Reputation: 1658

Access modifiers are used for encapsulation: they allow you to arrange your code in packages and classes, and have only an "official" public interface visible to the outside, while hiding the implementation details (which you want to do, so that you can later change it without telling anyone).

This is especially (only?) important, when you release code as a library for other programmers to use. Even if the code is only used in your own program, it helps to structure larger programs into several packages. - Thilo

Upvotes: 0

tdammers
tdammers

Reputation: 20721

Member visibility, as this feature is often called, is not a security feature. It is a convenience for the programmer, designed to help limit cross-class dependencies. By declaring a member private, you prevent other code from accessing it directly. This has two advantages:

  • if you find that a member variable gets manipulated in a way you did not intend, the amount of code you have to check is significantly smaller when the variable is private
  • you can change the inner workings of a class (everything that is declared private) without breaking the interface (everything declared public)

Member visibility is probably the most important language feature in realizing encapsulation, one of the core principles of object-oriented programming.

Upvotes: 7

BrokenGlass
BrokenGlass

Reputation: 160922

This is a basic OO concept - encapsulation and has mostly nothing to do with security per se. To quote from Wikipedia (emphasis mine):

Hiding the internals of the object protects its integrity by preventing users from setting the internal data of the component into an invalid or inconsistent state. A benefit of encapsulation is that it can reduce system complexity, and thus increases robustness, by allowing the developer to limit the interdependencies between software components.

Upvotes: 1

Related Questions