Andrew Lentvorski wrote:
Paul G. Allen wrote:
So, the way Linux does it is not bad at all, but the way programmers
fail to initialize the memory as soon as it's allocated *is* bad.
Allocate the memory and initialize it when it's allocated, not later
on when you *might* use it. That way, it's there up front, before the
long computation, and there's no surprises half way through. (This is
why the C or C++ compiler warns about uninitialized objects.)
You do embedded software? Right? And *still* make that statement?
Yes, and I can safely say that 100% of my embedded software has never
been released with a bug. Allocating memory to an object in ANY system
without properly initializing it to a known state is BAD BAD BAD.
Especially in a complex system.
I have fixed lots of embedded software written by others that failed to
do this, and in the process fixed bugs in said software. I've also fixed
PC software that failed to do this.
Programmers like you are the reason that all of the Moore's law gains go
directly into the trash, programs start up like sludge, and "Please
wait..." screens are the norm.
With a statement like that, it's pointless to discuss things further
with you.
PGA
--
Paul G. Allen, BSIT/SE
Owner, Sr. Engineer
Random Logic Consulting Services
www.randomlogic.com
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
