Timeline for Returning an int array from a function
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 29, 2019 at 11:40 | review | Low quality posts | |||
| Oct 29, 2019 at 12:50 | |||||
| Oct 14, 2016 at 19:11 | comment | added | Harper Shelby | Absolutely true - I didn't go in to all the details, just pointed out the basic strategies. In the Arduino environment, having tracked allocations (and in most cases, any dynamic allocations) is probably not the way to go, for the reasons you mention. | |
| Oct 14, 2016 at 18:59 | comment | added | Chris Stratton |
If you are going to allocate memory in the function/method be sure to do it in a lasting way - something placed on the stack for example will not outlive the return of the function call - it might still be there, but only unreliably. Personally I'd use either a static allocation, or the caller's stack, as lasting runtime allocation introduces failure modes and is going to require about as much space to track the allocation as the 6 bytes that 3 Arduino ints would actually consume.
|
|
| Oct 14, 2016 at 18:53 | history | answered | Harper Shelby | CC BY-SA 3.0 |