On 11/24/2010 11:45 AM, Jes Sorensen wrote:
On 11/24/10 18:43, Anthony Liguori wrote:
On 11/24/2010 11:36 AM, Jes Sorensen wrote:
On 11/24/10 18:27, Anthony Liguori wrote:
The compiler won't generate an error. Only upon a call to
file_release() will a null pointer dereference happens whereas in C++,
because this paradigm is structured in the language, the compiler can
help assist you.
Explicit code means you know what is going on, it means you can debug it
in gdb and match it. That is a *good* thing!
So I take it you avoid switch statements, while, or for loops in your C
code.
Those map easily to assembly code and gdb.
The mapping is definitely not simply especially after a couple rounds of
loop unrolling and code motion.
Regards,
Anthony Liguori
Jes
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
