I have confusion on allocate memory from Stack or Heap?
Anyone can demonstrate me with some code ?
which is allocated from Stack and which is from Heap
thanks : )
Printable View
I have confusion on allocate memory from Stack or Heap?
Anyone can demonstrate me with some code ?
which is allocated from Stack and which is from Heap
thanks : )
when you use new or malloc() the memory is normally allocated from the heap. When you allocate an object within a function, it goes on the stack
Code:void foo()
{
int x; <<< x is on the stack
char *ptr = new char[255]; <<< 255 characters are allocated in the heap
but ptr object is on the stack
int array[255]; <<< 255 ints are all on the stack
}
so whats the difrence?Quote:
Originally Posted by stober
The difference can be identified from the usage of the operator new. When it is used, you will be allocating memory from the heap and you need a pointer to store the address. As the memory from the stack, the variable has to be declared within a function without using operator new.
...provided that you know what is the stack and what is the heap...
If not, then look those terms up in any of the hundreds of text books at your local book store or library. You can even find the definitions in Websters online dictionery :rolleyes: http://dictionary.reference.com/search?q=heapQuote:
Originally Posted by Mercantilum
You can imagine the stack as being like a stack of plates. As soon as a function calls some other function things get added to the stack (from the bottom, upwards) starting with the return address (i.e. where the program flow should go back to, once the called function has finished).
Stack memory
Let's suppose there was nothing on the stack to begin with. One of the functions (either the calling function or the called function) would start a stack by placing a return address - and some extra 'plates' might be added, representing any arguments that get passed to the called function (the called function's parameters).
Program execution then gets passed to the called function which probably adds some more plates in the form of 'local variables'. Every 'plate' has some sort of information written on it that means something special to te program. By the time the called function reaches its return statement it has a big stack of plates. Just before it returns, it removes the plates (one by one) from the top downward so that it can read the return address, written on that very bottom plate. The program then jumps back to that original return address.
The most important thing about the stack is that you don't need to think much about it. Your program manages it. Also, stack management is very efficient because the plates don't literally need to be removed (like they would if they were real plates). In reality, the program contains a "stack pointer" that simply gets updated each time a particular plate needs to be written to or read from. The size of the stack is usually quite small because it's mostly used for local variables (variables that go out of scope pretty soon after they're finished with). The size of the stack is set at compile time and is small enough to be available on any computer, no matter how little RAM it's got.
Heap memory
The heap is a different thing altogether. Different PC's have different amounts of memory so it would be silly to have to allocate all the memory at compile time. If a particular computer has a lot of RAM, why not make use of it? Therefore the heap consists of memory that can be allocated at run time. The amount of heap memory is different for different machines and a well written program will take account of this (allocating heap memory sparingly - and not assuming that everyone will have massive amounts of it). Heap memory is most often used for 'large' things (e.g. the contents of a file) - or for things that need to 'stay around' in memory so that different functions can share the data (in other words, for NON-local variables). It's also used very frequently to allocate memory for things whose size is not known until run time. For example, if you had to open a file and read in the data, you don't know how much data exists until run time. In contrast, the size of objects allocated on the stack, needs to be known at compile time.
Whereas your program takes care of stack memory (allocating it & cleaning it up) it's the programmer's job to deal with heap memory. The size of objects allocated on the heap is often not known to the compiler - therefore the programmer must allocate and release the memory specifically.
The most difference between the stack and heap is you must manage the variable which allocate the memory from the heap -- allocate and callback--and the variable which allocate the memory from the stack will be allocated the memory by machine
...and calling the constructor too as it happens. Heap is be to totally your resposibility. What you allocate on to it, is your responsibility to be deleted once you are done with it. Else you get into a condition know as memory leaks which could be very un-healthy for you. Try allocations on stack as much as possible...on heap? only when you need it and u are sure of what you are doing.Quote:
Originally Posted by Kheun
The Stack is a Hardware Supported Feature in terms of Microprocessor Registers and Segments.
The Heap is actually a Software Abstraction.
For more information on the Stack, read this thread.
Also, on a side note - when one allocates using "new" one allocates on the Free Store.
Often, the Free Store is implemented as the "heap".
For more information on Free Store, Stack and Heap, please read this article.
Here is a sample code:
class A()
{
private:
int i;
char c;
public:
A();
};
void fun(A* a)
{
a = new A(); //allocated on heap(2nd time allocation)
}
int main()
{
A a; // allocated on stack
fun(&a);
}
Stack is where variables declared before runtime are stored.
Heap is where variables created or initialized at runtime are stored.
Here is another good site I found about heap and stack
What is heap and stack
Any more questions?
Only three...Quote:
Originally Posted by xjessie007
1) Why to you think the persion is waiting for an answer after 3.5 YEARS?
2) Why have you not enabled Private messaging as recommented in the "BEFORE you post announcement"
3) Why are you posting code without using code tags (as covered in the same referrecced material)?
:) sorry, I have not looked at the timestamps on the posts.
I haven't searched through the forum on how to enable private messaging, this functionality is usually enabled by default, so I haven't expected that it would be off by default or that someone would want to contact me righ away.
I do not see code tags here. As I am writing this post, there are no icons above this edit text box. (?)
Great answer to this question, with more details:
http://www.programmerinterview.com/i...tack-and-heap/
Which one of these three questions did you mean?Quote:
Originally Posted by jporter
:cool:Quote:
Originally Posted by TheCPUWizard