Thread: Confused with encapsulation

I am trying to grasp encapsulation and I am getting confused on a few points:

1. Local variables in other functions of the same class
When I want to access a variable which is local to another function of the same class, what do I have to do? I have read about accessor functions but I am not entirely sure if I get the concept.

2. Can pointers get around encapsulation? They seem to be powerful althought I am not entirely getting them completeley. And by looking at some rather complex code from other programmers (which I am trying to figure out), pointers can happily grab stuff out of scope.

3. Is there a comprehensive guide that specifically explains how to pass informations on different levels of scope? Trying to pass stuff around between different parts of the code has been a very confusing affair for me so far.

Originally Posted by Jefff

I am trying to grasp encapsulation and I am getting confused on a few points:

1. Local variables in other functions of the same class
When I want to access a variable which is local to another function of the same class, what do I have to do? I have read about accessor functions but I am not entirely sure if I get the concept.

Not possible.
Accessor functions are for accessing private members of the class.

2. Can pointers get around encapsulation? They seem to be powerful althought I am not entirely getting them completeley. And by looking at some rather complex code from other programmers (which I am trying to figure out), pointers can happily grab stuff out of scope.

Yes, they can. But that would be rather bad code to do do so.

3. Is there a comprehensive guide that specifically explains how to pass informations on different levels of scope? Trying to pass stuff around between different parts of the code has been a very confusing affair for me so far.

Err...There are only a few ways to pass stuff.
(By value, by reference and by address (There is also 'moving' but that is not the point here)).
You should have learnt those 3 in detail while learning about functions.

Originally Posted by Jefff

I have a function in a class that is using a pointer like so:

Code:

if (ptr->group == SomeIntegerValue)

The function gets *ptr passed as a parameter from something else which I do not entirely understand yet. Therefore I plan to get around that by having another pointer(from another function in the same class) that accesses SomeIntegerValue like this.
And what would be the correct syntax to do so?

I don't understand what you are trying to get around.
The 'ptr' points to an object.
group is a data member of that object.
If won't be accessible if it is private, pointer or not. (If the object is of the same class, it'll be.)
Since you say that existing code does that, it already is public, or friend-zoned !

Following manasijs advice I practiced the basics a bit more an I came up with a solution.
I copied the value from the pointer into a member variable which I created for this purpose which then could be accessed by other functions of the same class.

However I still do not understand how the pointer was able to deliver the data to one of the functions in the first place.

No idea. Your problem description here is completely unclear.

I could post the relevant bits of the code here, but I did not want to do so because I feared looking like some idiot that is asking for someone else to do the hard work for me.

In that case, why not find an example of how one of those other pointers are fishing things out? And do the same.

From what you describe, however, that "large game engine" is not practicing encapsulation in any useful form. I interpret your expression "pointers fishing out things all over the place appears to be very common" as "pointers are being used to bypass encapsulation".

That is a sign of either poor design of the game engine, or inappropriate usage of that game engine by hackers. Or both.

I'll look deeper into it. Also I do not claim the engine is badly programmed or something. Probably me just having difficulty to understand more complex code.