From mboxrd@z Thu Jan  1 00:00:00 1970
From: 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
Message-ID: <patchbomb.1301571489@localhost.localdomain>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: xen-devel@lists.xensource.com
Cc: Ian Campbell <ian.campbell@citrix.com>
List-Id: xen-devel@lists.xenproject.org

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.