On Thu, 7 Feb 2008, Ian Jackson wrote:
Johannes Schindelin writes ("Re: [Qemu-devel] [PATCH] avoid name clashes due to
LIST_* macros"):
Read what you wrote. By that reasoning you cannot use _any_ name in qemu,
because qemu should bend over to be mixable with other code.
No,
Johannes Schindelin writes ("Re: [Qemu-devel] [PATCH] avoid name clashes due to
LIST_* macros"):
> Read what you wrote. By that reasoning you cannot use _any_ name in qemu,
> because qemu should bend over to be mixable with other code.
No, not at all. Just that when a clash h
Hi,
On Thu, 7 Feb 2008, Ian Jackson wrote:
> Anthony Liguori writes ("Re: [Qemu-devel] [PATCH] avoid name clashes due to
> LIST_* macros"):
> > Ian Jackson wrote:
> >
> > > qemu's audio subdirectory contains a copy of BSD's sys-queue.h,
> >
Anthony Liguori writes ("Re: [Qemu-devel] [PATCH] avoid name clashes due to
LIST_* macros"):
> Ian Jackson wrote:
> > qemu's audio subdirectory contains a copy of BSD's sys-queue.h, which
> > defines a bunch of LIST_ macros. This makes it difficult to build a
Ian Jackson wrote:
qemu's audio subdirectory contains a copy of BSD's sys-queue.h, which
defines a bunch of LIST_ macros. This makes it difficult to build a
program made partly out of qemu and partly out of the Linux kernel[1],
since Linux has a different set of LIST_ macros. It might also caus
qemu's audio subdirectory contains a copy of BSD's sys-queue.h, which
defines a bunch of LIST_ macros. This makes it difficult to build a
program made partly out of qemu and partly out of the Linux kernel[1],
since Linux has a different set of LIST_ macros. It might also cause
trouble when mixing
