Jump to content

[SOLVED] Private Members and Acessor Methods


hkothari

Recommended Posts

So lately I've been just making all members of my classes private and created accessor methods to get the values, but no operation is done to a lot of these members, it's just returning the values and that's it. Is there a reason to do this or not to do it? It has been common practice for me in other languages, but I feel like it isn't necessary in this case.

So lately I've been just making all members of my classes private and created accessor methods to get the values, but no operation is done to a lot of these members, it's just returning the values and that's it. Is there a reason to do this or not to do it? It has been common practice for me in other languages, but I feel like it isn't necessary in this case.

 

Well, IMO, it depends on the operations being done on the data.  If you're merely treating the object as a collection of data that can be stored and/or retrieved, you could define it as something like a PHP version of a struct by keeping the data members public.  If you're doing anything more advanced/complex, keep the encapsulation in place.

 

 

Archived

This topic is now archived and is closed to further replies.

×
×
  • 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.