When is it best to use the stack instead of the heap and vice versa?

by

Use the stack when your variable will not be used after the current function returns. Use the heap when the data in the variable is needed beyond the lifetime of the current function.

More Related Contents:

  1. cin and getline skipping input [duplicate]
  2. Uses of C comma operator [duplicate]
  3. C++ std::set update is tedious: I can’t change an element in place
  4. Deploying Qt 5 App on Windows
  5. Why SDL defines main macro?
  6. Function with missing return value, behavior at runtime
  7. ‘size_t’ vs ‘container::size_type’
  8. how do I print an unsigned char as hex in c++ using ostream?
  9. difference between a pointer and reference parameter?
  10. Object creation on the stack/heap?
  11. Why are NULL pointers defined differently in C and C++?
  12. How to set file permissions (cross platform) in C++?
  13. What happens to the pointer itself after delete? [duplicate]
  14. Which Boost features overlap with C++11?
  15. Now that we have std::array what uses are left for C-style arrays?
  16. C++ int to byte array
  17. Reason for C++ member function hiding [duplicate]
  18. Difference between using #include and #include in C++
  19. Why does nvcc fails to compile a CUDA file with boost::spirit?
  20. What happens when I assign a number larger than INT_MAX to an int?
  21. C++ convert vector to vector
  22. std::fstream buffering vs manual buffering (why 10x gain with manual buffering)?
  23. What is going on with bitwise operators and integer promotion?
  24. Why do some experienced programmers write comparisons with the value before the variable? [duplicate]
  25. C++ terminate called without an active exception
  26. What does int() do in C++?
  27. Where should non-member operator overloads be placed?
  28. Why would I std::move an std::shared_ptr?
  29. difference between pointer to an array and pointer to the first element of an array
  30. Wrapping FILE* with custom std::ostream

Leave a Comment