C (programming language): Difference between revisions
No edit summary |
|||
Line 11: | Line 11: | ||
Memory allocated by <code>alloca</code> is allocated on the stack and will automatically be freed. Do not call <code>free</code> on this memory. Do not allocate more than a few bytes using <code>alloca</code> or you will risk a stack overflow leading to undefined behavior.<br> | Memory allocated by <code>alloca</code> is allocated on the stack and will automatically be freed. Do not call <code>free</code> on this memory. Do not allocate more than a few bytes using <code>alloca</code> or you will risk a stack overflow leading to undefined behavior.<br> | ||
For automatic garbage collection, use [[C++]] which has smart pointers. | For automatic garbage collection, use [[C++]] which has smart pointers. | ||
{{ hidden | <code>_malloca</code> | | |||
On Windows you also have: | |||
* <code>_malloca</code> | |||
* <code>_calloca</code> | |||
These are not portable so I wouldn't use them. They are a safer version of <code>alloca</code> which allocates to the heap if there isn't enough stack space. However, you need to free them using <code>_freea</code> which eliminates the main benefit of <code>alloca</code>.<br> | |||
As far as I can tell, the only benefit is to prevent heap fragmentation. | |||
}} |
Revision as of 20:21, 9 February 2021
C is the low-level programming language taught in UMD's CMSC216 class.
Usage
Memory Allocation
#include <stdlib.h>
There are 3 ways to allocate memory in C
malloc(bytes)
Allocated memory is uninitialized.calloc(number, bytes)
Allocated memory is initialized to 0. Allocates (number * bytes) bytes of memory.alloca(bytes)
Discouraged
Memory allocated by malloc
and calloc
are on the heap and should be deallocated by free
when no longer used to avoid memory leaks.
Memory allocated by alloca
is allocated on the stack and will automatically be freed. Do not call free
on this memory. Do not allocate more than a few bytes using alloca
or you will risk a stack overflow leading to undefined behavior.
For automatic garbage collection, use C++ which has smart pointers.
_malloca
On Windows you also have:
_malloca
_calloca
These are not portable so I wouldn't use them. They are a safer version of alloca
which allocates to the heap if there isn't enough stack space. However, you need to free them using _freea
which eliminates the main benefit of alloca
.
As far as I can tell, the only benefit is to prevent heap fragmentation.