What reasonable amount of accessor functions do you need in a C++ class?

Thompson Lee · 2011-04-29T09:22:41

I tend to notice that if you have a class for a certain requirement, chances are there will be a lot of accessor methods wrapped nicely in the C++ class itself. (Possibly Java) I'm curious to know what is the reasonable amount of accessor methods for a class with any one of the following requirements: 1. Game engine: How many are there, do you think that's reasonable enough for maintenence and easier scripting? 2. Mutator methods: Since modifying a variable requires pair(s) of accessor methods, I wondered if we could control the amount of them while implementing a class? 3. Nested accessor methods: Just in case, if C++ allows you to invoke a mutator method via an accessor method, how do we reduce the amount of accessor methods? Thanks in advance.

For Beginners

Started by tom_mai78101 April 28, 2011 09:42 PM

9 comments, last by 21st Century Moose 12 years, 11 months ago

21st Century Moose

13,459

April 29, 2011 09:22 AM

Generally you need one for each member that needs one.

I am being serious here; there is no fixed amount that is prescribed under any particular circumstances; your code follows your design and not some abstract rules like "you need X amount of thing Y". If your design requires 200, then you need 200. If your design requires 1 then you need 1. Simple as that.

Direct3D has need of instancing, but we do not. We have plenty of glVertexAttrib calls.

What reasonable amount of accessor functions do you need in a C++ class?

This topic is closed to new replies.

Popular Topics

Recommended Tutorials

What reasonable amount of accessor functions do you need in a C++ class?

This topic is closed to new replies.

Popular Topics

Recommended Tutorials

Reticulating splines