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-api

[Xen-API] Problem in "xen_event_record" structure

To: xen-api@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-API] Problem in "xen_event_record" structure
From: "chetan saundankar" <chetan.lists@xxxxxxxxx>
Date: Sat, 29 Dec 2007 01:17:26 +0530
Delivery-date: Fri, 28 Dec 2007 11:47:39 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type; bh=XyCOELhgFocaT6lfGVnOqcsM4O2yMrL3s7QBX4gJJAo=; b=cNLZnD2Uk6VB86uoLZ5aRF7PnIe2rBXRD0e8ZNXzoaczcLBjeD8pqUFc4q/BzDQe+CuYdXtXSVAi1bRE5vV2lGOefnlpp2p5nq8d6sS2onrrNNSJR6c/GoSkxlN3Wkz2lYjgNQO13b5Lkz7re57v6rFj3po7novuUm3Ca+eUlZM=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=vjfVxaNPijG8HFl/m0p08JfpN7TtDg1nH/xUXZ7ZqCyiMwkq9JDSozZtHpbOyUfKRfzZfIaMzPwrGaBeJBRBpQ1Uh3ozIVaCJ9thhxuNiWTR1UC7Q/tTeAQWM4nuWJbfgQLlYuYoR8t9q1ouAuYg8YztCpxChxePT3As+x1Hqv0=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-api-request@lists.xensource.com?subject=help>
List-id: Discussion of API issues surrounding Xen <xen-api.lists.xensource.com>
List-post: <mailto:xen-api@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-api-bounces@xxxxxxxxxxxxxxxxxxx
Hi,
Compilation of C++ user code with xen api header file "xen_event.h" fails because of a char* field named "class" in "xen_event_record" structure.

typedef struct xen_event_record
{
    int64_t id;
    time_t timestamp;
    char *class;
    enum xen_event_operation operation;
    char *ref;
    char *obj_uuid;
} xen_event_record;

I have also observed that " __cplusplus" macros are not used in the header files which requires caller to use extern "C" while using the library with C++ code.

Regards
Chetan

_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-api
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-API] Problem in "xen_event_record" structure, chetan saundankar <=