[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-devel] recent major -unstable changes cause ia64 build to be broken

  • To: "Hollis Blanchard" <hollisb@xxxxxxxxxx>
  • From: "Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>
  • Date: Tue, 10 May 2005 16:05:33 -0700
  • Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Tue, 10 May 2005 23:05:25 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcVVqImojOtuKU5lS5arw9lxAg/NHwAC6VGQ
  • Thread-topic: [Xen-devel] recent major -unstable changes cause ia64 build to be broken

> it. Here I
> will repeat my point about relying on implicit includes... :)

Though I agree in principle with not using implicit includes,
it doesn't really work in reality.  For example, many
header files declare structs that use typedefs for elements
of the struct, which creates a direct dependency on a header
file.  The only way to avoid including the header file directly
in the "parent" header file is by "instructing" all the users
of the "parent" header to first include the subsidiary ones.
The C language doesn't deal with this very well, resulting
in very obscure error messages if something is missing.
And since typedefs cannot be duplicately declared even if
identical (a bug in C I think), there's a catch-22.


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.