Re: Using Get() and Set() instead of accessing the variable directly

I agree with the Get() statement being public.
I suppose I just make it either private or protected so it is not accessible
and shows that it is not needed by other classes.
The const statement must be when using references or pointers?
Thanks for the info. It makes sense and is good practice!

I guess I never use the const statement just because, I just know that I am
using it.
If I need to modify something, I usually create a statement like.
void GetX(int* x){ *x = m_x; }or void GetX(int& x)( x = m_x; }
instead of
int* GetX(){ return &m_x; } or int& GetX(){ return m_x; }
I see a lot of Microsoft code do it that way, so I just follow their
example.
It makes sense and is a coding style that I prefer.
That way, there is no confusion as to what the return type should be.


I guess that all depends on how the variable is being used.
It could be either private, public or protected.
If it is private to the class, then it is private.
If it can be modified by subclasses, then it should be protected.
If it can be modified by other classes, then it should be public.
That would be application specific.

Something like an Addition class would need to be declared public for
example.
Addition.SetX(1);
Addition.SetY(2);
Addition.Add();
Ans = Addition.GetResult();

"jmarc" <jmarc@incursion-voyages.com> wrote in message
news:D3_Lh.112455$Du6.75270@edtnps82...