From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JD2cn-0000KW-HB for qemu-devel@nongnu.org; Thu, 10 Jan 2008 13:59:33 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JD2cl-0000IH-L7 for qemu-devel@nongnu.org; Thu, 10 Jan 2008 13:59:32 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JD2ck-0000I4-Mh for qemu-devel@nongnu.org; Thu, 10 Jan 2008 13:59:30 -0500 Received: from main.gmane.org ([80.91.229.2] helo=ciao.gmane.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1JD2ck-00074M-G3 for qemu-devel@nongnu.org; Thu, 10 Jan 2008 13:59:30 -0500 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1JD2cZ-0008PU-L8 for qemu-devel@nongnu.org; Thu, 10 Jan 2008 18:59:19 +0000 Received: from 204.147.152.1 ([204.147.152.1]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 10 Jan 2008 18:59:19 +0000 Received: from consul by 204.147.152.1 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 10 Jan 2008 18:59:19 +0000 From: "consul" Date: Thu, 10 Jan 2008 10:59:10 -0800 Message-ID: References: <1199871092.4337.4.camel@frecb07144> <1199873069.4337.20.camel@frecb07144> <1199880481.4337.31.camel@frecb07144> <1199883098.4337.42.camel@frecb07144> <1199957735.4773.22.camel@frecb07144> <1199967143.4773.38.camel@frecb07144> <47861E01.6050709@qumranet.com> Sender: news Subject: [Qemu-devel] Re: [PATCH] Fix double backslash problem in Windows Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org "Avi Kivity" wrote in message news:47861E01.6050709@qumranet.com... > Johannes Schindelin wrote: >> Hi, >> >> On Thu, 10 Jan 2008, Laurent Vivier wrote: >> >> >>> Perhaps the best solution is to put "file=" option at the end of >>> aliases, '\0' is marking the end of filename (it is likely the idea of >>> andrzej about special characters). >>> >> >> Oh, why not just make it a requirement that file= comes last, always? >> >> > > That's hardly intuitive. I would prefer some sort of escaping for \, and > \=. It will also break if/when -drive gains another filename argument > (say, for keeping shapshot data in). > > -- > error compiling committee.c: too many arguments to function > > > > Why not use double quotes around parameter values containing special characters?