Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb@sources.redhat.com
Subject: Re: [RFA] New substitute-path commands
Date: Thu, 13 Jul 2006 21:41:00 -0000	[thread overview]
Message-ID: <20060713214123.GA4967@nevyn.them.org> (raw)
In-Reply-To: <20060713212746.GA1519@adacore.com>

On Thu, Jul 13, 2006 at 02:27:46PM -0700, Joel Brobecker wrote:
> My question is the following: When you enter a second rule, should it
> take precedence over the first one you entered? More generally, should
> the substitution rules entered last be used first, or the opposite?

Good question.  I'm strongly in favor of intelligent users picking
rules where it doesn't make a difference! :-)

> I'm 50-50 on this:
> 
>    . With first-entered/first-used, you enter the rules following the
>      logic "if blah, then replace with [...]; else if bloh, then replace
>      with [...]; else if [...], then [...]". In other words, you enter
>      the rules in the same order you would write a "program". It seems
>      pretty natural.
> 
>    . With last-entered/first-used, it's possible to override previous
>      entries without having to delete the previous rules. Not so natural
>      to "program", though.
> 
> Actually, as I'm writing this, I now favor first-entered/first-used.
> One can delete a rule if he wants to override it. It's marginal anyway.
> 
> What do you guys think?

I think that's fine.

Let's not overdesign this.  I was only half-kidding about calling a
Python function to transform the source pathnames if you want to do
anything more complicated - if someone comes up with a legitimate use
for anything more complex than a simple list of prefixes, we can do
something along those lines.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2006-07-13 21:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20060707052219.GA971@adacore.com>
     [not found] ` <u8xn5rbx7.fsf@gnu.org>
     [not found]   ` <20060707191203.GD971@adacore.com>
     [not found]     ` <uhd1sp9uv.fsf@gnu.org>
     [not found]       ` <20060710054027.GF971@adacore.com>
     [not found]         ` <ud5cdnsml.fsf@gnu.org>
     [not found]           ` <20060710214706.GA2390@adacore.com>
     [not found]             ` <20060710215114.GA31444@nevyn.them.org>
     [not found]               ` <20060710215630.GB2390@adacore.com>
     [not found]                 ` <20060710215839.GA31772@nevyn.them.org>
2006-07-13 21:27                   ` Joel Brobecker
2006-07-13 21:41                     ` Daniel Jacobowitz [this message]
2006-07-14 10:37                     ` Eli Zaretskii
2006-07-14 13:06                       ` Daniel Jacobowitz
2006-07-14 13:43                         ` Eli Zaretskii
2006-07-14 13:46                           ` Daniel Jacobowitz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060713214123.GA4967@nevyn.them.org \
    --to=drow@false.org \
    --cc=brobecker@adacore.com \
    --cc=gdb@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox