WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [PATCH 2 of 9] libxl: return libxl_dominfo from libxl_ev

Stefano Stabellini writes ("Re: [Xen-devel] [PATCH 2 of 9] libxl: return 
libxl_dominfo from libxl_event_get_domain_death_info"):
> enum alone would OK, but most header files contains other stuff as well,
> so including features.h would be fine but including platform.h would not.
> In order to have a clear policy we should just say that including Xen
> header files should be avoided.

I don't think there is any difficulty with libxl callers #including
Xen public header files, no matter that those Xen header files have
lots of other stuff in that is not relevant to them.

It's not as if #including the Xen public headers exposes functions for
making hypercalls, or indeed any functions or objects at all.

Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>