From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Nuil8-0006SH-1Y for qemu-devel@nongnu.org; Thu, 25 Mar 2010 04:49:46 -0400 Received: from [140.186.70.92] (port=46856 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Nuil6-0006Rz-OT for qemu-devel@nongnu.org; Thu, 25 Mar 2010 04:49:45 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1Nuil3-0003kc-PV for qemu-devel@nongnu.org; Thu, 25 Mar 2010 04:49:44 -0400 Received: from mx1.redhat.com ([209.132.183.28]:54946) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1Nuil3-0003kU-79 for qemu-devel@nongnu.org; Thu, 25 Mar 2010 04:49:41 -0400 Message-ID: <4BAB2398.7000704@redhat.com> Date: Thu, 25 Mar 2010 10:49:28 +0200 From: Avi Kivity MIME-Version: 1.0 Subject: Re: [Qemu-devel] Re: [libvirt] Supporting hypervisor specific APIs in libvirt References: <4BA7C40C.2040505@codemonkey.ws> <20100323145105.GV16253@redhat.com> <4BA8D8A9.7090308@codemonkey.ws> <201003231557.19474.paul@codesourcery.com> <4BA8E6FC.9080207@codemonkey.ws> <4BA901B5.3020704@redhat.com> <4BA9A066.3070904@redhat.com> <20100324103643.GB624@redhat.com> <4BA9EC88.6000906@redhat.com> <20100324134250.38822113@redhat.com> <4BAA6CD9.6060001@redhat.com> <20100324171219.4365318b@redhat.com> <4BAA76EA.2060601@codemonkey.ws> <20100324182501.000b69a7@redhat.com> <4BAA86C2.4020701@codemonkey.ws> <4BAB1E21.8080009@snarc.org> In-Reply-To: <4BAB1E21.8080009@snarc.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Vincent Hanquez Cc: "libvir-list@redhat.com" , qemu-devel@nongnu.org, Paul Brook , Luiz Capitulino On 03/25/2010 10:26 AM, Vincent Hanquez wrote: > On 24/03/10 21:40, Anthony Liguori wrote: >>> If so, what C clients you expected beyond libvirt? >> >> Users want a C API. I don't agree that libvirt is the only C >> interface consumer out there. > > (I've seen this written too many times ...) > How do you know that ? did you do a poll or something where *actual* > users vote/tell ? > > From my point of view, i wouldn't want to write a high level > management toolstack in C, specially > since the API is well defined JSON which is easily available in all > high level language out there. > Strongly agreed. Even the managementy bits of qemu (anything around QObject) are suffering from the lowleveledness of C. -- error compiling committee.c: too many arguments to function