Re: [PATCH] type safe allocator
From: Miklos Szeredi
Date: Thu Aug 02 2007 - 09:50:07 EST
> >> On Aug 2 2007 16:04, Alexey Dobriyan wrote:
> >> >On 8/2/07, Miklos Szeredi <miklos@xxxxxxxxxx> wrote:
> >> >> fooptr = kmalloc(sizeof(struct foo), ...);
> >> >
> >> >Key word is "traditional". Good traditional form which even half-competent
> >> >C programmers immediately parse in retina.
> >>
> >> And being aware of the potential type-unsafety makes programmers more
> >> careful IMHO.
> >
> >That's a _really_ good reason ;)
>
> Yes, a good reason not to use g_new(), so people do get bitten when
> they are doingitwrong.
Should we turn off all warnings then, to make people more careful
after constantly being bitten by stupid mistakes?
That's one way to think of it, yes. But I think most would agree,
that we have better things to do than being careful about things that
the compiler can check for us.
Miklos
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/