qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: Antony Pavlov <antonynpavlov@gmail.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Peter Crosthwaite <peter.crosthwaite@xilinx.com>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] a QOM Coding Conventions question
Date: Mon, 16 Dec 2013 15:17:23 +0100	[thread overview]
Message-ID: <52AF0B73.3090403@suse.de> (raw)
In-Reply-To: <20131215151709.be54fbe34245cae757ba0279@gmail.com>

Am 15.12.2013 12:17, schrieb Antony Pavlov:
> Can we use more detailed comments? E.g.
> 
>      typedef struct {
>          /*< QOM service fields >*/
>          MyParentClass parent_class;
>          /*< class private fields >*/
> 
>          [any fields you need]
>      } FooClass;

Since those comments wouldn't be supported by gtk-doc, the short answer
is we can't.

The longer answer, as explained in the other reply, is that it's a
question of who contributes and more importantly maintains long-term the
tools to process these and all the /** ... */ comments.

Regards,
Andreas

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

      reply	other threads:[~2013-12-16 14:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-13 20:26 [Qemu-devel] a QOM Coding Conventions question Antony Pavlov
2013-12-14 23:06 ` Peter Crosthwaite
2013-12-14 23:42   ` Peter Maydell
2013-12-14 23:51     ` Peter Crosthwaite
2013-12-15  9:02       ` Pantelis Koukousoulas
2013-12-16 12:48         ` Peter Crosthwaite
2013-12-16 13:26           ` Andreas Färber
2013-12-15 11:17   ` Antony Pavlov
2013-12-16 14:17     ` Andreas Färber [this message]

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=52AF0B73.3090403@suse.de \
    --to=afaerber@suse.de \
    --cc=antonynpavlov@gmail.com \
    --cc=peter.crosthwaite@xilinx.com \
    --cc=peter.maydell@linaro.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).