> If we want to avoid the retyping (which is IMHO the most clean
> separation for all cases, even if it involves drudgery) then separating
> out code into libc-only headers would be nice.
Not that I think anyone is going to take me up on this, judging from prior
experience ...
... but if we are looking for a clean solution to types and constants that
are needed to communicate between kernel and user space, IMO the thing to
do is to define these in some sort of generic format, and have a tool to
generate actual headers from that according to whatever kernel, libc or
whoever wants to see. Possibly more than one tool as requirements differ.
That generic format *could* be a restricted form of C (restricted to only
those features needed for this task), but need not be.
The tool in question is not all that difficult to write; *if* people think
this is the right way to go (and agree on some of the necessary details),
I could write it. In C, even, so it doesn't need extra tools.
MfG Kai
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/