Search:

This is all irrelevant, and I assure you my understanding is solid (thanks to you folks); likely your digression is latency from my poor explanation and communication. I was messing around and for...

Okay so only local variables are stored in stack. Which are handled when it returns. My question was how does the JVM delete a lower iteration (push/rearranging). And, what do you mean because to my...

Never mind I found it. You guys were right from the beginning I should have just done some more research. It has to do with re-arranging to delete an item not on the top, I can do this in many...

Are you saying that local variables (non-static) aren't stored in the stack (I realize references might be stored in heap)? Heap is for objects and static variables is it not, so garbage collector...

Assume they are both local, and what if I want to delete s first?

Instantiate an object set values, then instantiate a new object and set values now try and delete the former object (all on the same thread).

For norm this is the one thing I mentioned.


When I said:


It was in an indirect manner. Say I have some values under a region in the stack now what if I happen to delete an object's...

Well for the sake of this conversation let us just trust in my diagnostic ability. The google term you suggested answered one of my questions, but I am still thinking it is seriously inefficient to...

I did mention in my initial post some changes I could make, but I would like to just move past this and deal strictly with the questions I asked if you don't mind.

The issue is less of my concern I am mostly just curious about this: "So I suppose the real questions are: A, does java only have one stack per thread, B, what takes place in a stack to delete values...

I was recently running into some issues with non-static variables, I think it might be my tenuous understanding of stack memory. So java only gets one stack per thread? And if this is the case it...