From: Avi Kivity <avi@redhat.com>
To: quintela@redhat.com
Cc: Developers qemu-devel <qemu-devel@nongnu.org>,
KVM devel mailing list <kvm@vger.kernel.org>
Subject: Re: KVM call minutes for November 29
Date: Tue, 29 Nov 2011 18:59:40 +0200 [thread overview]
Message-ID: <4ED50F7C.2040903@redhat.com> (raw)
In-Reply-To: <8762i3nczx.fsf@trasno.mitica>
On 11/29/2011 05:51 PM, Juan Quintela wrote:
> How to do high level stuff?
> - python?
>
One of the disadvantages of the various scripting languages is the lack
of static type checking, which makes it harder to do full sweeps of the
source for API changes, relying on the compiler to catch type (or other)
errors.
On the other hand, the statically typed languages usually have more
boilerplate. Since one of the goals is to simplify things, this
indicates the need for a language with type inference.
On the third hand, languages with type inferences are still immature
(golang?), so we probably need to keep this discussion going until an
obvious choice presents itself.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-11-29 16:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-29 15:51 KVM call minutes for November 29 Juan Quintela
2011-11-29 16:59 ` Avi Kivity [this message]
2011-11-29 19:10 ` [Qemu-devel] " Markus Armbruster
2011-11-30 1:18 ` Juan Quintela
2011-12-01 9:32 ` [Qemu-devel] " Avi Kivity
2011-11-29 22:59 ` Anthony Liguori
2011-11-30 9:22 ` Alon Levy
2011-11-30 9:54 ` [Qemu-devel] " Daniel P. Berrange
2011-11-30 13:54 ` Anthony Liguori
2011-11-30 14:35 ` Alon Levy
2011-11-30 14:38 ` Anthony Liguori
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=4ED50F7C.2040903@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.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).