5,321
edits
C (programming language): Difference between revisions
→Memory Allocation
| Line 13: | Line 13: | ||
There is also a way to dynamically allocate memory on the stack. | There is also a way to dynamically allocate memory on the stack. | ||
* <code>alloca(bytes)</code> Usage is [https://stackoverflow.com/questions/1018853/why-is-the-use-of-alloca-not-considered-good-practice Discouraged] | * <code>alloca(bytes)</code> Usage is [https://stackoverflow.com/questions/1018853/why-is-the-use-of-alloca-not-considered-good-practice Discouraged] | ||
Memory allocated by <code>alloca</code> is allocated on the stack and will automatically be freed at the end of the function, not scope. 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 at the end of the function, not scope.<br> | ||
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++]] smart pointers or Rust instead. | For automatic garbage collection, use [[C++]] smart pointers or Rust instead. | ||