On Tue, Mar 20, 2018 at 02:54:37PM +0100, Max Reitz wrote: > But I guess the main advantage with using this rule I see is that it's > better for people reading the code. It's just nice to know whether a > file belongs to qemu or not by just looking at the #include statement. > (Note that this implies that it is indeed more difficult to determine > whether a header belongs to qemu than whether it sits in the same > directory as the C file, though!) So I think the old (current) rule is > better for reading code, Michael's rule would be better for writing > code. I think reading code is what should be easier.
How about prefixing all internal headers with qemu/ ? That's a way to avoid namespace collisions that is actually standard. -- MST _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
