This looks as opprotunity for more innovation. It may happen that all three approaches will be embraced - write new code for critical apps, device auto convert utilites for some predictable code and change code manually.
The author has made a very valid point, which comes at the problem from a different point of view, but points at the same disaster, running out of memory and crashing to a halt. As Mr Anderson points out, memory is a big deal, and it is far from infinite. While I don't understand fully the differences between IPV4 and IPV6, his point about the memory problems is certainly valid enough to make one ask "is this really a good idea?" And the prospect of programs just continuing to allot memory space and then not release it does certainly describe a very real and very fatal fault in a lot of current code. And the description of the effort needed to make changes is sort of depressing, I think.
NASA's Orion Flight Software Production Systems Manager Darrel G. Raines joins Planet Analog Editor Steve Taranovich and Embedded.com Editor Max Maxfield to talk about embedded flight software used in Orion Spacecraft, part of NASA's Mars mission. Live radio show and live chat. Get your questions ready.
Brought to you by