Android Question Erels 'Code modules and classes': returns a deleted list-item?

17: No, it can never happen that you have a dangling pointer. The object will only be garbage collected when there are no references to it. As long as you can reach the object in some way, its memory will not be released.

Erel said:

17: No, it can never happen that you have a dangling pointer. The object will only be garbage collected when there are no references to it. As long as you can reach the object in some way, its memory will not be released.

Click to expand...

So the pointer is removed from the list (16), but the objekt still lives on?

We aren't really talking about pointers here. The object is removed from the list however it is still alive as the local 'res' variable holds a reference to that object.

Thanks Erel!
(It seems do be not the same: 'reference' and 'pointer to that object'?)

Pflichtfeld said:

(It seems do be not the same: 'reference' and 'pointer to that object'?)

Click to expand...

The context is different. Pointer is a C / C++ term and it is a low level feature. The pointer is the actual memory address.
Reference (not C++ reference) is a bit more ambiguous and higher level concept. You hold a reference to an object. You don't know the memory address and you aren't responsible for managing the memory yourself. From the developer perspective the variable holds the object the only thing that you need to remember is that the object is never copied.

Thanks. Was very helpful!