From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: KVM call minutes for November 29 Date: Tue, 29 Nov 2011 18:59:40 +0200 Message-ID: <4ED50F7C.2040903@redhat.com> References: <8762i3nczx.fsf@trasno.mitica> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Developers qemu-devel , KVM devel mailing list To: quintela@redhat.com Return-path: In-Reply-To: <8762i3nczx.fsf@trasno.mitica> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org Sender: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org List-Id: kvm.vger.kernel.org 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