-
We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.
Stack vs. Heap
- Thread starter mikeshn
- Start date
Nothinman
Elite Member
Google is your friend.
From here :
Stack allocation is a work of compiler. All stack variables are automatic. When variable is out of scope, compilere deletes stack objects automatically. The stack is memory area that temporarily holds the arguments to the function as well as any variables that are defined local to the function.
The heap is a separate area from the program and the stack.You use new ( malloc in C) and delete(free in C) to allocate and deallocate objects in heap memory. The advantage if using new and delete is they provide an efficient wat to allocate and deallocate memory.
From here :
Stack allocation is a work of compiler. All stack variables are automatic. When variable is out of scope, compilere deletes stack objects automatically. The stack is memory area that temporarily holds the arguments to the function as well as any variables that are defined local to the function.
The heap is a separate area from the program and the stack.You use new ( malloc in C) and delete(free in C) to allocate and deallocate objects in heap memory. The advantage if using new and delete is they provide an efficient wat to allocate and deallocate memory.