Thread: When to handle memory explicitly?

But in an embedded environment, heap space is just as precious. In some such, it's even non-existent.

Originally Posted by CornedBee

But in an embedded environment, heap space is just as precious. In some such, it's even non-existent.

true enough; I was doing coding on a medical device in the early part of this decade with exactly that issue....my example comes from working on (more recently) PS3 where stack, while there, is at a premium.

The point that was being made though was (hopefully) all the world is not an Intel with gobs of stack and heap.

Originally Posted by Bubba

Thread bumping only applies to threads at least 14 days old. You are 'replying' to this thread since you are well within that window.

I work in an embedded environment. Daily I run into issues with no swapping to disk, no loading from disk (after the intial load), not enough heap and/or fragmented heap, and video memory issues. Not many problems with stack memory but I have run into a couple of stack overflows. Heap and video memory are primarily the biggest issues I have to overcome from day to day.

Yeah but there is just something about working embedded where it seems the odds are against you to really test your skills....it is ironic that on the PC the only direction to go it seems is "BIGGER" whereas in the embedded world it is often "smaller" or learning to do without portions of the language.

"What do you mean there's no flock()??"

Sorry for the drift...