Search Results
| Search type | Search syntax |
|---|---|
| Tags | [tag] |
| Exact | "words here" |
| Author |
user:1234 user:me (yours) |
| Score |
score:3 (3+) score:0 (none) |
| Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
| Views | views:250 |
| Code | code:"if (foo != bar)" |
| Sections |
title:apples body:"apples oranges" |
| URL | url:"*.example.com" |
| Saves | in:saves |
| Status |
closed:yes duplicate:no migrated:no wiki:no |
| Types |
is:question is:answer |
| Exclude |
-[tag] -apples |
| For more details on advanced search visit our help page | |
Results tagged with stack
Search options questions only
not deleted
user 242470
A LIFO (Last In, First Out) data structure.
14
votes
6
answers
5k
views
Is there a drawback at allocating a huge amount of the stack for a single array in an embedd...
I usually have no problem deciding whether some data has to be global, static or on the stack (No dynamic allocation here, so no use of the heap). … (that might be 50% or more of the stack)
Could someone share some experience with this kind of situation, or do someone think about any valid reason not to put this array on the stack? …
- 453