Robby Ames wrote:...I know that method's code stay in heap but method's calls stay in stack.
Keep Smiling Always — My life is smoother when running silent. -paul
[FAQs] [Certification Guides] [The Linux Documentation Project]
"Il y a peu de choses qui me soient impossibles..."
Robby Ames wrote:So what's the need of knowing 'how memory allocation work in java', because we are not going to create a new JVM. But I think it's a good question. In a forum, a users commented on main().
"Leadership is nature's way of removing morons from the productive flow" - Dogbert
Articles by Winston can be found here
"Il y a peu de choses qui me soient impossibles..."
Stevens Miller wrote:I believe the most useful response is not just, "You don't need to be worried about that, " but, rather, "You don't need to be worried about that because [reason why Java makes this unimportant...]."
"Leadership is nature's way of removing morons from the productive flow" - Dogbert
Articles by Winston can be found here
"Il y a peu de choses qui me soient impossibles..."
Stevens Miller wrote:Is that, then, a valid question? That is, does it make sense to ask, "How can I create objects to support operations instead of to encapsulate data?" Am I even on a meaningful line of inquiry here?
"Leadership is nature's way of removing morons from the productive flow" - Dogbert
Articles by Winston can be found here
Winston Gutkowski wrote:
And I hate to say, but it took 8 years, two languages (C++ and Java) and a "moment of clarity" (and believe me, I've had precious few of those in my life) to finally "get it".
Akhilesh Trivedi wrote:
Robby Ames wrote:...I know that method's code stay in heap but method's calls stay in stack.
What do you mean by "method's code"? Objects are stored on heap, wherever they are created.
Stevens Miller wrote:This discussion might help you.
Campbell Ritchie wrote:Which forum? Give us a link? What did they say? Did anybody disagree?
Winston Gutkowski wrote:
And that's just scratching the surface.
And knowing these things, while it might be interesting, is of very little use to you as a programmer. You can't change any of it, and the chances of it making any difference to how you write a program are almost nil - indeed, you should never write programs that rely on something you may have read about it, because it's quite possible that it will change in a future release - the Java memory model has already changed many times since the language first came out.
Winston
Stevens Miller wrote:This discussion might help you.
Robby Ames wrote:I know, it may not be useful in programming but it will definitely help me to understand the language in a better way.
"Leadership is nature's way of removing morons from the productive flow" - Dogbert
Articles by Winston can be found here
"Il y a peu de choses qui me soient impossibles..."
Robby Ames wrote: I'm only asking for a drop of your knowledge.
"Il y a peu de choses qui me soient impossibles..."
Stevens Miller wrote:
Robby Ames wrote: I'm only asking for a drop of your knowledge.
Heh. Drops are relative. For some of these other guys, it may be a drop. From me, you've just had the full bucket.
Robby Ames wrote:I was hoping for a precise answer from the experienced guys like you.
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime. |