From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [Qemu-devel] KVM call minutes for November 29 Date: Thu, 01 Dec 2011 11:32:25 +0200 Message-ID: <4ED749A9.1050700@redhat.com> References: <8762i3nczx.fsf@trasno.mitica> <4ED50F7C.2040903@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: quintela@redhat.com, Developers qemu-devel , KVM devel mailing list To: Markus Armbruster Return-path: Received: from mx1.redhat.com ([209.132.183.28]:8821 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752510Ab1LAJc2 (ORCPT ); Thu, 1 Dec 2011 04:32:28 -0500 In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: On 11/29/2011 09:10 PM, Markus Armbruster wrote: > Avi Kivity 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. It was just off the radar for me. We should consider it, by all means. -- error compiling committee.c: too many arguments to function