On Tue, Jul 12, 2011 at 05:47:22PM -0400, Mike Frysinger wrote: > > I would consider sanctity of the namespace pretty irrelevant when > > you're using a highly Linux-specific feature. Certainly there's no > > standard document that says signalfd.h can't include fcntl.h because > > it's not covered by any standard to begin with. > > while true, the purist in me still finds it distasteful ;). and what > is Linux-specific today could be in POSIX tomorrow! just look at the > all the fun new funcs in 2008 vs 2004 specs to see this isnt > unthinkable.
Well all these *fd interfaces intended to be used with select/poll/epoll are pretty much just a manifestation of disagreement over POSIX's adoption of threads as the solution to asynchronous event handling... > >> - most, but not all, arches are the same (but maybe i remember this wrong) > > > > Why do the kernel developers keep doing idiotic things like this? > > *sigh* > > well, once you're stuck with an overlapping pile, there's really > nothing you can do to sort them out. you might be able to blame the > original source, but past that, they're pretty much pucked. Well they could be consistent and either say everything new is going to use universal generic constants and structures with clean alignment, or they could say they're always going to reuse the existing arch-specific stuff. But reusing it on some archs and using new generics on others make a whole new meta level of arch-dependence that's even a bigger pain to deal with. Rich _______________________________________________ uClibc mailing list [email protected] http://lists.busybox.net/mailman/listinfo/uclibc
