Jump to content

The point of encapsulating public variables


proggR

Recommended Posts

This sounds like a very newbie question I know but is there any real reason to prefer getter/setter accessor methods in situations when all they do is get and set the values of variables? It seems to me thats adding a function call when its not necessary.

I understand the point of having some variables inaccessible to outside classes or even only allowing access to things that extend your class. I can also see when you may want to only allow one or the other method of access to a variable. But is there any benefit when you're allowing both via the accessor methods anyway?

 

Maybe I'm just thinking out loud when I'm tired but I figured someone here may know.

 

Thanks in advance.

Link to comment
Share on other sites

This thread is more than a year old. Please don't revive it unless you have something important to add.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.