From: David Gibson <david@gibson.dropbear.id.au>
To: "Andreas Färber" <afaerber@suse.de>
Cc: "Daniel P. Berrange" <berrange@redhat.com>,
peter.maydell@linaro.org, qemu-devel@nongnu.org,
pbonzini@redhat.com, armbru@redhat.com, lcapitulino@redhat.com
Subject: Re: [Qemu-devel] [RFC 0/4] QOM class properties - do we need them?
Date: Fri, 30 Sep 2016 09:36:39 +1000 [thread overview]
Message-ID: <20160929233639.GK30519@umbus.fritz.box> (raw)
In-Reply-To: <2f804b68-2438-b877-e4c3-be48e6d12000@suse.de>
[-- Attachment #1: Type: text/plain, Size: 1235 bytes --]
On Thu, Sep 29, 2016 at 12:23:41PM +0200, Andreas Färber wrote:
> Am 29.09.2016 um 12:21 schrieb Daniel P. Berrange:
> > On Thu, Sep 29, 2016 at 12:12:32PM +0200, Andreas Färber wrote:
> >> Am 29.09.2016 um 10:14 schrieb Daniel P. Berrange:
> >>> Practically all instances properties should become class properties
> >>> as its going to save wasting memory once most are converted.
> >>
> >> Not all, but most. child<> properties were the reason to have properties
> >> on the instance.
> >
> > That's why I said "Practically all", instead of just "all" :-)
>
> To me as non-native speaker "practically" is the opposite of
> "theoretically". :)
Heh, more English corner cases. "Theoretically" and "in theory" mean
the same thing, but "practically" and "in practice" don't. Or.. they
do in theory, but not in practice :p. For bonus confusion, saying
"practically speaking" would, in this context, mean what you expected,
but "practically" on its own doesn't - it means basically the same as
"almost" or "nearly".
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-09-29 23:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-29 0:16 [Qemu-devel] [RFC 0/4] QOM class properties - do we need them? David Gibson
2016-09-29 0:16 ` [Qemu-devel] [RFC 1/4] qcrypto: Remove usage of class properties David Gibson
2016-09-29 0:16 ` [Qemu-devel] [RFC 2/4] s390: Don't use " David Gibson
2016-09-29 0:16 ` [Qemu-devel] [RFC 3/4] tests: Remove tests for " David Gibson
2016-09-29 0:16 ` [Qemu-devel] [RFC 4/4] qom: Abolish " David Gibson
2016-09-29 7:52 ` [Qemu-devel] [RFC 0/4] QOM class properties - do we need them? Paolo Bonzini
2016-09-29 8:14 ` Daniel P. Berrange
2016-09-29 10:12 ` Andreas Färber
2016-09-29 10:21 ` Daniel P. Berrange
2016-09-29 10:23 ` Andreas Färber
2016-09-29 23:36 ` David Gibson [this message]
2016-10-04 9:51 ` Kevin Wolf
2016-09-29 23:33 ` David Gibson
2016-09-30 8:06 ` Daniel P. Berrange
2016-09-29 10:16 ` Andreas Färber
2016-09-29 23:37 ` David Gibson
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=20160929233639.GK30519@umbus.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=afaerber@suse.de \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=pbonzini@redhat.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).