qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Roman Kiryanov <rkir@google.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
	JP Cottin <jpcottin@google.com>,
	Erwin Jansen <jansene@google.com>
Subject: Re: QEMU headers in C++
Date: Thu, 2 May 2024 09:02:10 +0100	[thread overview]
Message-ID: <ZjNIOfJdmLGAJnKh@redhat.com> (raw)
In-Reply-To: <CAOGAQeq+Wu9wiBj+tF0PJHMZS-F4KnVBOXCyXhYQsm+REyLUpg@mail.gmail.com>

On Wed, May 01, 2024 at 09:40:16PM -0700, Roman Kiryanov wrote:
> Hi QEMU,
> 
> I work in Android Studio Emulator and we would like to develop devices
> in C++. Unfortunately, QEMU headers cannot be used with C++ as is
> (e.g. they use C++ keywords as variable names or implicitly cast void*
> to T*).

NB, in recent past QEMU explicitly eliminated almost[1] all C++ code from
the tree, because the consensus was to be exlcusively a C project. 

> Will QEMU be open to accept patches from us to make QEMU headers C++
> compatible?

Personally I think that'd be a retrograde step. Any downstream development
fork that made use of that facility would be not be able to feed changes
/ additions back into upstream QEMU codebase at a later date, without QEMU
accepting C++ code once again.

We'll never control what forks can do, and many will never feed back code
regardless, but IMHO we should be steering external developers in a way
that keeps open the door for their changes to be merged back upstream.

With regards,
Daniel

[1] Only some minor windows installer code remains C++.
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|



  parent reply	other threads:[~2024-05-02  8:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-02  4:40 QEMU headers in C++ Roman Kiryanov
2024-05-02  6:19 ` Thomas Huth
2024-05-02 14:47   ` Warner Losh
2024-05-02  8:02 ` Daniel P. Berrangé [this message]
2024-05-02 15:17   ` Peter Maydell
     [not found] <a href="raw">
     [not found] ` </a>
2024-05-02 15:19   ` Paolo Bonzini
2024-05-02 16:04     ` Roman Kiryanov

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=ZjNIOfJdmLGAJnKh@redhat.com \
    --to=berrange@redhat.com \
    --cc=jansene@google.com \
    --cc=jpcottin@google.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rkir@google.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 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).