Stack vs Heap in C/Java

Question

Here's my understanding.

In C programming, if I do int a then that a is created on stack and thus the memory is taken from stack. Heap plays no part here.

But if I do something like

int *a;
a=(int*)malloc(sizeof(int));

and dynamically allocate the memory, then the reference variable will be placed on stack, but the memory it points to will be on the heap.

Am I correct with my understanding?

Now, I picked up this book on java that says

Whenever you need an object, you simply write the code to create it by using new, and the storage is allocated on the heap when that code is executed.

So there's no way of creating objects on Stack in Java?

I guess, the primitive data types can still be placed on stack, but I am concerned about the Objects.

Answer 1

There is no way to create objects on the stack in Java. Java also has automatic garbage collection, so you don't have any way of deleting objects. You just let all references to them go out of scope and eventually the garbage collector deals with them.