> > I wonder why we don't have type safe object allocators a-la new() in > > C++ or g_new() in glib? > > > > fooptr = k_new(struct foo, GFP_KERNEL); > > > > is nicer and more descriptive than > > > > fooptr = kmalloc(sizeof(*fooptr), GFP_KERNEL); > >... > > But it's much more likely to break when someone converts fooptr to a > different struct. > > It might not be a common case but it sometimes happens - and your type > safe variant introduces the possibility for really nasty bugs.
The compiler would emit a warning about assigning to a pointer of different type. That's a fairly strong hint that something just broke. Miklos - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
