Re: [PATCH kvm-unit-tests 2/4] Introduce a C++ wrapper for the kvm APIs

Avi Kivity
2010-11-24T17:51:40Z

On 11/24/2010 07:43 PM, Jes Sorensen wrote:
> On 11/24/10 18:41, Avi Kivity wrote:
> > On 11/24/2010 07:36 PM, 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!
> >
> > Implicit code means that you don't need to debug it. The compiler gets
> > it right every time.
>
> Except when it doesn't,

Which is very rare, at least compared to my bug rate.

> or when you don't know why something happened
> and you ended up where you did....

There's always a disassembler.

--
error compiling committee.c: too many arguments to function