> Folks, this is serious. _We_ might be used to having in effect a C dialect > with extensions implemented by preprocessor. That's fine, but for a fresh > reader it becomes a problem; sure, they can dig in include/linux/*.h and > to some extent they clearly have to. However, it doesn't come for free > and we really ought to keep that in mind - amount of local idioms (and > anything that doesn't look like a normal function call with normal arguments > _does_ become an idiom to be learnt before one can fluently RTFS) is a thing > to watch out for.
That's why the g_new() form that glib uses makes some sense. It borrows an idiom from C++, and although we all know C++ is a horrid language, to some extent lots of people are familiar with it. > IOW, whenever we add to that pile we ought to look hard at whether it's worth > the trouble. Well, this is not some earth-shattering stuff, but I think it would be good to have. I got used to it in glib, and I miss it in linux. I understand the knee-jerk reaction of most people who are unfamiliar with it, and I can do nothing about that. If there's no positive feedback I'll just give up, it's not that I can't live with the current situation. 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/
