This week's book giveaway is in the Kotlin forum.
We're giving away four copies of Kotlin in Action and have Dmitry Jemerov & Svetlana Isakova on-line!
See this thread for details.
Win a copy of Kotlin in Action this week in the Kotlin forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

Dan's definition of encapsulated class  RSS feed

 
Barkat Mardhani
Ranch Hand
Posts: 787
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
All three classes are tightly encapsulated, because the data members are private. A tightly encapsulated class can have public accessor and mutator methods, but it is not required to have those methods.

Is that universally accepted definition?
 
P Veer
Greenhorn
Posts: 9
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Yes.I think so.Accessor and mutator methods are only used to get access of these private data members outside the class.If they too are declared private or protected it doesn't make sense to write these additional methods.
 
P Veer
Greenhorn
Posts: 9
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
It is not required to have those methods since they are only used to access private data members.If you want to restrict the access to private data members within the class there is no need for creating accesors and mutators.
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!