From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15820 invoked by alias); 11 Jul 2006 20:45:43 -0000 Received: (qmail 15812 invoked by uid 22791); 11 Jul 2006 20:45:43 -0000 X-Spam-Check-By: sourceware.org Received: from nile.gnat.com (HELO nile.gnat.com) (205.232.38.5) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 11 Jul 2006 20:45:41 +0000 Received: from localhost (localhost [127.0.0.1]) by filtered-nile.gnat.com (Postfix) with ESMTP id D60D448CE15 for ; Tue, 11 Jul 2006 16:45:39 -0400 (EDT) Received: from nile.gnat.com ([127.0.0.1]) by localhost (nile.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 10405-01-10 for ; Tue, 11 Jul 2006 16:45:39 -0400 (EDT) Received: from takamaka.act-europe.fr (S0106000625ac85e1.vs.shawcable.net [70.71.27.110]) by nile.gnat.com (Postfix) with ESMTP id 91BB648CE97 for ; Tue, 11 Jul 2006 16:45:39 -0400 (EDT) Received: by takamaka.act-europe.fr (Postfix, from userid 507) id 0574247EFA; Tue, 11 Jul 2006 13:45:39 -0700 (PDT) Date: Tue, 11 Jul 2006 20:45:00 -0000 From: Joel Brobecker To: gdb-patches@sourceware.org Subject: Re: [RFA] New substitute-path commands Message-ID: <20060711204538.GB1262@adacore.com> References: <20060705215606.GF3580@adacore.com> <20060705230129.GA1145@nevyn.them.org> <20060706044733.GC673@adacore.com> <1152198199.6282.63.camel@dufur.beaverton.ibm.com> <20060706162952.GB24631@nevyn.them.org> <20060707052219.GA971@adacore.com> <20060711124739.GA18324@nevyn.them.org> <20060711203042.GA1262@adacore.com> <20060711203328.GA30744@nevyn.them.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060711203328.GA30744@nevyn.them.org> User-Agent: Mutt/1.4i Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2006-07/txt/msg00096.txt.bz2 > The reason for anchoring is to reduce surprising behavior. Especially > since this only replaces one occurance, it seems like the path of least > astonishment. For instance, "substitute-path foo bar" would replace > /fool with /barl and /tmp/myfoo with /tmp/mybar. That makes really good sense. I now prefer anchoring too. Since we're anchoring the start, it might make sense to anchoring the end as well, if only for consistency. -- Joel