From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:53121) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RauBi-0008HR-Hy for qemu-devel@nongnu.org; Wed, 14 Dec 2011 14:08:23 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RauBh-0003iu-1a for qemu-devel@nongnu.org; Wed, 14 Dec 2011 14:08:22 -0500 Received: from e6.ny.us.ibm.com ([32.97.182.146]:40689) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RauBg-0003il-VH for qemu-devel@nongnu.org; Wed, 14 Dec 2011 14:08:21 -0500 Received: from /spool/local by e6.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Wed, 14 Dec 2011 14:08:19 -0500 Received: from d01av01.pok.ibm.com (d01av01.pok.ibm.com [9.56.224.215]) by d01relay01.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id pBEJ3Dv0214352 for ; Wed, 14 Dec 2011 14:03:13 -0500 Received: from d01av01.pok.ibm.com (loopback [127.0.0.1]) by d01av01.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id pBEJ39Ec012671 for ; Wed, 14 Dec 2011 14:03:10 -0500 Message-ID: <4EE8F2EB.4090106@us.ibm.com> Date: Wed, 14 Dec 2011 13:03:07 -0600 From: Anthony Liguori MIME-Version: 1.0 References: <1323879637-16901-1-git-send-email-aliguori@us.ibm.com> <1323879637-16901-2-git-send-email-aliguori@us.ibm.com> <4EE8F0D4.3050300@weilnetz.de> In-Reply-To: <4EE8F0D4.3050300@weilnetz.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 1/4] memory: make memory API parsable by gtkdoc-scan List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stefan Weil Cc: qemu-devel@nongnu.org, Avi Kivity On 12/14/2011 12:54 PM, Stefan Weil wrote: > Am 14.12.2011 17:34, schrieb malc: >> On Wed, 14 Dec 2011, Anthony Liguori wrote: >> >>> GTK/glib uses a convenient of: >>> >>> typedef struct _CamelCase CamelCase; >>> >>> The reason that they use a separate struct name is that in C++, the struct >>> namespace not a separate namespace from the type namespace. This is actually a >>> reasonable policy for QEMU to adopt as we eventually start exporting C libraries >>> that may be consumed by C++ programs. >>> >>> I think the use of _ does not violate the C specification as the struct >>> namespace is not the same as the type namespace which is what the C spec refers >>> to if I understand it correctly. >> >> It does violate the standard _ followed by upper case letter is reserved >> in all contexts. > > sCamelCase instead of _CamelCase seems to work, too. Are you sure? Take a look at: html/QEMU-Memory-API.html#MemoryRegionOps It's supposed to look like: http://wiki.qemu.org/docs-internal/QEMU-Memory-API.html#MemoryRegionOps Regards, Anthony Liguori