<p>Absolutely;what kind of hardware can’t handle malloc(sizeof(MAX_INT)) :)???</p>
<p>In reality, real time programming makes one think twice about too many malloc’s, free’s, new’s, and the like. Not only because of possibility of nasty memory leaks, but because our stuff has to ‘not fail’ in the general sense. So, we really have to code review every malloc/new to make sure it gets free’d and so on. </p>
<p>Also, pointer operations and the like are generally frowned upon, even for strings and such, because of the possibility of ever crashing due to a blown pointer. Lots of beloved library functions are verboten and we have our own versions… </p>
<p>Writing software for consumer devices sometimes gets to be a pain…</p>