Re: C++ pushback

Avi Kivity
2006-04-25T08:42:29Z

Xavier Bestel wrote:
> In the first case you know that exactely *one* kmalloc(GFP_KERNEL)
> occurs. In the second case you have to browse SuperBlock's constructor
> to check if it allocates things, needs to run with/without interrupts,
> PREEMPT, whatever... (not even talking about exceptions).
>
That seems to be a case against writing functions.

Why is a C function acceptable where a C++ constructor isn't?

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