From: "Andreas Färber" <afaerber@suse.de>
To: 陳韋任 <chenwj@iis.sinica.edu.tw>
Cc: Michael Tokarev <mjt@tls.msk.ru>,
qemu-devel@nongnu.org, Evgeny Voevodin <e.voevodin@samsung.com>,
Dmitry Solodkiy <d.solodkiy@samsung.com>
Subject: Re: [Qemu-devel] QOM: why "klass" used instead of "class" ?
Date: Thu, 01 Mar 2012 09:14:03 +0100 [thread overview]
Message-ID: <4F4F2FCB.20605@suse.de> (raw)
In-Reply-To: <20120229090547.GA80051@cs.nctu.edu.tw>
Am 29.02.2012 10:05, schrieb 陳韋任:
> On Wed, Feb 29, 2012 at 10:59:54AM +0400, Michael Tokarev wrote:
>> On 29.02.2012 09:52, Evgeny Voevodin wrote:
>>> include/qemu/object.h:
>> []
>>> * void my_device_class_init(ObjectClass *klass, void *class_data)
>>> * {
>>> * DeviceClass *dc = DEVICE_CLASS(klass);
>>> * dc->reset = my_device_reset;
>>> * }
>>> *
>>>
>>> Why to use "klass", not "class"?
>>
>> Because in C++, "class" is a reserved word. It is quite typical idiom
>> to replace class with klass in (public) headers.
>
> I thought QEMU is written in C, right? Is there anything related to C++?
A while back there was a patch that added a C++ audio backend, for
instance. I didn't get around to cleaning the patch up yet though.
Objective-C is used for the Cocoa frontend.
At least our headers should work with such C-derived languages.
clazz is another common alternative if you don't like klass. ;)
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2012-03-01 8:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-29 5:52 [Qemu-devel] QOM: why "klass" used instead of "class" ? Evgeny Voevodin
2012-02-29 6:59 ` Michael Tokarev
2012-02-29 9:05 ` 陳韋任
2012-02-29 9:22 ` Evgeny Voevodin
2012-03-01 8:14 ` Andreas Färber [this message]
2012-03-01 8:17 ` malc
2012-03-01 8:28 ` Andreas Färber
2012-03-01 8:29 ` malc
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=4F4F2FCB.20605@suse.de \
--to=afaerber@suse.de \
--cc=chenwj@iis.sinica.edu.tw \
--cc=d.solodkiy@samsung.com \
--cc=e.voevodin@samsung.com \
--cc=mjt@tls.msk.ru \
--cc=qemu-devel@nongnu.org \
/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.