site_archiver@lists.apple.com Delivered-To: darwin-kernel@lists.apple.com I'm not sure, but I have a hunch that Michael might be in a similar situation as I am. In any case, let me hypothetically assume that he is. --> Developing open source for BSD kernels, ported to several major variants (Free, Open, Mac OS X, ...) non-commercially. When you are in this situation, there is a constant tradeoff between using the Apple KPIs vs maintaining a common code base for all the BSD variants you are ported to. Personally, I've grown rather fond of the Apple KPIs and would be happy to see other BSD variants adopt them, but that just ain't gonna happen. Just thought I'd throw in this perspective, rick _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists.a... I've ended up with a compromise, where I use the KPIs when it is easy to do so (and easy to replace the calls with generic BSD code like vp->v_type, if the core team for that variant deems it necessary) and going beyond/around the KPIs when I can create a code base that works on all the variants I'm ported to, using macros and other tricks. And, yes, it is only appropriate for folks in the open source, non-commercial camp, like me. This email sent to site_archiver@lists.apple.com