public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Juan Quintela <quintela@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Avi Kivity <avi@redhat.com>,
	Developers qemu-devel <qemu-devel@nongnu.org>,
	KVM devel mailing list <kvm@vger.kernel.org>
Subject: Re: KVM call minutes for November 29
Date: Wed, 30 Nov 2011 02:18:35 +0100	[thread overview]
Message-ID: <87y5uymmqc.fsf@trasno.mitica> (raw)
In-Reply-To: <m3sjl6zqvx.fsf@blackfin.pond.sub.org> (Markus Armbruster's message of "Tue, 29 Nov 2011 20:10:26 +0100")

Markus Armbruster <armbru@redhat.com> wrote:
> Avi Kivity <avi@redhat.com> writes:
>
>> 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.
>
> I wouldn't call ML immature.  But I wouldn't call it a scripting
> language, either.

ocaml (Standard ML is a big monster) is not inmature.  But depending on
how much we want to implement on it, its integral types are not very
good.

- no unsigned types
- signed types are 31 and 63 bits wide, sniff.

And its object system is ...... bizarre?
On the other side, inference is quite understable, and its type
inference works pretty well.  And doing stubs with * is tedious, but not
difficult at all.

Later, Juan.

  reply	other threads:[~2011-11-30  1:18 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
2011-11-29 19:10   ` [Qemu-devel] " Markus Armbruster
2011-11-30  1:18     ` Juan Quintela [this message]
2011-12-01  9:32     ` 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=87y5uymmqc.fsf@trasno.mitica \
    --to=quintela@redhat.com \
    --cc=armbru@redhat.com \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.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