From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25559 invoked by alias); 27 Aug 2011 08:45:07 -0000 Received: (qmail 25443 invoked by uid 22791); 27 Aug 2011 08:45:04 -0000 X-SWARE-Spam-Status: No, hits=-1.3 required=5.0 tests=AWL,BAYES_00,SPF_SOFTFAIL X-Spam-Check-By: sourceware.org Received: from mtaout20.012.net.il (HELO mtaout20.012.net.il) (80.179.55.166) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sat, 27 Aug 2011 08:44:49 +0000 Received: from conversion-daemon.a-mtaout20.012.net.il by a-mtaout20.012.net.il (HyperSendmail v2007.08) id <0LQK00200W9OEV00@a-mtaout20.012.net.il> for gdb-patches@sourceware.org; Sat, 27 Aug 2011 11:44:31 +0300 (IDT) Received: from HOME-C4E4A596F7 ([84.228.21.112]) by a-mtaout20.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0LQK001IWW9PWAC0@a-mtaout20.012.net.il>; Sat, 27 Aug 2011 11:44:14 +0300 (IDT) Date: Sat, 27 Aug 2011 08:45:00 -0000 From: Eli Zaretskii Subject: Re: [RFA] 12843 In-reply-to: To: Tom Tromey Cc: keiths@redhat.com, gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: <83liuffdlo.fsf@gnu.org> References: <4E56C5A0.60802@redhat.com> <4E57E9EC.8060706@redhat.com> X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2011-08/txt/msg00522.txt.bz2 > From: Tom Tromey > Cc: gdb-patches@sourceware.org > Date: Fri, 26 Aug 2011 13:07:34 -0600 > > My view is that, aside from the drive-letter case, we should require > funny file names to be quoted. Agreed. > I am not sure how to handle file names with quotes; IIUC typical > escaping syntax won't work because it is already used in DOS-style file > names. This matters since I think MI clients already have to play funny > games here :-( Can we standardize on quoting with ".." instead? If so, DOS file names will not be a problem, because DOS/Windows filesystems don't allow the `"' character in file names. Therefore, \" can be safely interpreted as a literal double quote character. If we must use '..' style quoting, then how about doubling the ' to express a literal quote character? > Furthermore I think that quoted text should always be a token: we should > not try to extend the token boundaries or break the token up. That is: > > Valid: break 'file.c':function > Invalid: break 'file.c:function' > Invalid: break 'file'.c:function What about these: break 'file with spaces.c:function:with:colons' break 'file with spaces.c':'function:with:colons' ? Do you propose just the latter to be valid?