diff options
author | Ian Campbell <ian.campbell@citrix.com> | 2010-08-19 15:20:22 +0100 |
---|---|---|
committer | Ian Campbell <ian.campbell@citrix.com> | 2010-08-19 15:20:22 +0100 |
commit | bcbf6e2049191fb218ff288106d0744430011dc9 (patch) | |
tree | 71c2df6b88cd195dd16acb201ed854dc9477c252 /.hgignore | |
parent | 735f084c0f41c313c07bcd345f0abf2850e90c4e (diff) | |
download | xen-bcbf6e2049191fb218ff288106d0744430011dc9.tar.gz xen-bcbf6e2049191fb218ff288106d0744430011dc9.tar.bz2 xen-bcbf6e2049191fb218ff288106d0744430011dc9.zip |
libxl: generate destructors for each libxl defined type
I chose the name "_destroy" rather than "_free" because the destructor
functions will free only the members of a type recursively but will
not free the actual type structure itself. The allocation of the type
is typically done by the caller and may not be a single allocation,
e.g. lists/arrays of types or embedded in other structures etc.
The exceptions to this rule are libxl_string_list_destroy and
libxl_key_value_list_destroy but I'm not 100% convinced they are
exceptions (since they are kind-of opaque) and I couldn't see a
cleanerway to express this concept. I have made a best effort attempt
to implement these functions sanely but since as far as I can tell
nothing in the current code base ever sets
libxl_domain_create_info.{xsdata,platformdata} I'm flying somewhat
blind.
[PATCH 05 of 16 of
libxl: autogenerate type definitions and destructor functions]
Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
Signed-off-by: Ian Jackson <ian.jackson@eu.citrix.com>
Diffstat (limited to '.hgignore')
-rw-r--r-- | .hgignore | 1 |
1 files changed, 1 insertions, 0 deletions
@@ -182,6 +182,7 @@ ^tools/libxen/test/test_bindings$ ^tools/libxen/test/test_event_handling$ ^tools/libxl/_.*\.h$ +^tools/libxl/_.*\.c$ ^tools/libxl/libxlu_cfg_y\.output$ ^tools/libxl/xl$ ^tools/libaio/src/.*\.ol$ |