All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: xen-devel@lists.xensource.com
Cc: Ian Campbell <ian.campbell@citrix.com>
Subject: [PATCH 0 of 4] [V2] libxl: Add enumeration type to IDL
Date: Thu, 31 Mar 2011 12:38:09 +0100	[thread overview]
Message-ID: <patchbomb.1301571489@localhost.localdomain> (raw)

As part of this I namespace some enum values, firstly within the
LIBXL_ namespace (which is clearly a good idea) but secondly to
namespace the values to within their respective typename, which is
less clearly of benefit. It makes the IDL for enumerations somewhat
cleaner but I'm not totally wedded to it -- opinions welcome.

Changes since first version:

  - Use typedef enum FOO { } FOO idiom which allows existing users of
    "enum FOO xxx;" to continue working.

  - Add libxl_compat.h which defines the old names in an attempt to
    retain API (but not ABI) compatibility. By default all previous
    APIs will be exposed. Not sure if it makes more sense to require
    users to specify which they want.

             reply	other threads:[~2011-03-31 11:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-31 11:38 Ian Campbell [this message]
2011-03-31 11:38 ` [PATCH 1 of 4] libxl: typedef libxl_action_on_shutdown Ian Campbell
2011-03-31 18:39   ` Ian Jackson
2011-03-31 11:38 ` [PATCH 2 of 4] libxl: move all enum values into the libxl namespace Ian Campbell
2011-03-31 18:40   ` Ian Jackson
2011-03-31 11:38 ` [PATCH 3 of 4] libxl: namespace enum values within their type Ian Campbell
2011-03-31 11:38 ` [PATCH 4 of 4] libxl: add an Enumeration type to the IDL, use it for all enums Ian Campbell
2011-03-31 11:42   ` Ian Campbell
2011-03-31 18:41     ` Ian Jackson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=patchbomb.1301571489@localhost.localdomain \
    --to=ian.campbell@citrix.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.