From: "François Revol" <revol@free.fr>
To: Avi Kivity <avi@redhat.com>
Cc: aliguori@us.ibm.com, lcapitulino@redhat.com,
filip.navara@gmail.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [PATCH 3/3] Introduce QNumber data type
Date: Thu, 06 Aug 2009 16:05:37 +0200 CEST [thread overview]
Message-ID: <804085774-BeMail@laptop> (raw)
In-Reply-To: <4A7AE302.30304@redhat.com>
> On 08/06/2009 04:52 PM, Luiz Capitulino wrote:
> > +
> > +typedef struct QNumber {
> > + QObject base;
> > + union {
> > + int n_int;
> > + int64_t n_int64;
> > + } number;
> > +} QNumber;
> >
>
> Why not have an int64_t exclusively?
>
> Also, we need floating point support. So probably need to split this
> into QInt and QFloat.
Aw you sure all this won't clash with some Qt class if some fold tries
to mix both?
Now, I use the BeAPI so I don't really care, but still.
And I still wonder why not just use a real OO language instead of
faking.
François.
next prev parent reply other threads:[~2009-08-06 14:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-06 13:52 [Qemu-devel] [PATCH RFC 0/3] QEMU Object Model Luiz Capitulino
2009-08-06 13:52 ` [Qemu-devel] [PATCH 1/3] Introduce qobject header file Luiz Capitulino
2009-08-06 14:02 ` [Qemu-devel] " Avi Kivity
2009-08-06 14:07 ` Luiz Capitulino
2009-08-06 15:54 ` [Qemu-devel] " malc
2009-08-06 13:52 ` [Qemu-devel] [PATCH 2/3] Introduce QString data type Luiz Capitulino
2009-08-06 13:52 ` [Qemu-devel] [PATCH 3/3] Introduce QNumber " Luiz Capitulino
2009-08-06 14:04 ` [Qemu-devel] " Avi Kivity
2009-08-06 14:05 ` François Revol [this message]
2009-08-06 14:48 ` Avi Kivity
2009-08-06 14:10 ` Luiz Capitulino
2009-08-06 21:21 ` Luiz Capitulino
2009-08-06 14:06 ` [Qemu-devel] Re: [PATCH RFC 0/3] QEMU Object Model Avi Kivity
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=804085774-BeMail@laptop \
--to=revol@free.fr \
--cc=aliguori@us.ibm.com \
--cc=avi@redhat.com \
--cc=filip.navara@gmail.com \
--cc=lcapitulino@redhat.com \
--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.