Re: SET, CLR, ISSET in types.h for _KERNEL builds

On Wed, 5 Jul 2006, M. Warner Losh wrote:

:In message: <28872.1151526546@xxxxxxxxxxxxxxxxxx>
: "Poul-Henning Kamp" <phk@xxxxxxxxxxxxxx> writes:
:: In message <20060628150227.R75801@xxxxxxxxxxxxxxxxx>, "Andrew R. Reiter" writes
:: :
:: >
:: >I apologize for top posting, but I lost the email that I think my
:: >point/question pertains to.
:: >
:: >Part of this seems to be for compatibility / merging from drivers of other
:: >OSes, no? If I am wrong, ignore me :-). If this is the case, would it be
:: >better to create some common other area for things of this nature so that
:: >it suffices to allow builds, but does not infect other areas of our own
:: >code base?
::
:: That's what I proposed too: #include <sys/netbsd_compat.h>
:
:This is even lamer. It makes no sense to invent a stupid place for a
:compatibility define. Might as well put the definition of NULL in
:limits.h.
:
:I'm killing this idea because people hate it.

Please explain which "idea" you're killing ... because your post-July 4th
attitude does not make it clear.

THANKS!


:
:Warner
:
:

--
arr@xxxxxxxxxx
_______________________________________________
freebsd-arch@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-arch
To unsubscribe, send any mail to "freebsd-arch-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: SET, CLR, ISSET in types.h for _KERNEL builds
    ... :>I apologize for top posting, but I lost the email that I think my ... :>point/question pertains to. ...
    (freebsd-arch)
  • Re: Correct previous post
    ... I apologize for the error. ... Below's the previous post in case it gets lost. ... posting outside of your original thread makes things harder for those of us trying to help you. ...
    (microsoft.public.windowsxp.general)