mbligh@aracnet.com said:
> That's not true either. There are lots of header files under the
> include tree that aren't externally useful.
It may be honoured more in the breach than the observance, but it's a custom
nonetheless.
> And every other header file is under the include path ... putting them
> all mixed in with C files is just making a mess.
No, look at e.g. SCSI. We have a scsi.h file in drivers/scsi which defines
subsystem specific things that we only use within SCSI. We have
include/scsi/scsi.h which defines things other subsystems can use.
> Que? How is include/asm-i386 any more "kernel core" than arch/i386?
Because the files are spreading. I think there's value to keeping something
tightly contained unless you're going to encourage others to use it.
Interfaces are dangerous things: If you release them into the wild
willy-nilly, they can come back and bite you (athough more often they just
bite other people).
James
-
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/
This archive was generated by hypermail 2b29 : Sat Nov 23 2002 - 22:00:40 EST