From: Daniel Jacobowitz <drow@false.org>
To: Andrew STUBBS <andrew.stubbs@st.com>
Cc: Eli Zaretskii <eliz@gnu.org>, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Use search path for scripts
Date: Fri, 25 Nov 2005 21:26:00 -0000 [thread overview]
Message-ID: <20051125191116.GH736@nevyn.them.org> (raw)
In-Reply-To: <4387585E.9050302@st.com>
On Fri, Nov 25, 2005 at 06:30:54PM +0000, Andrew STUBBS wrote:
> I see your point about changing the search algorithm though. Although
> even then, it might be more intuitive to always use the same algorithm
> for both. Is it likely to change?
Very. That search algorithm has (should have) more concepts of
"directory" to deal with than apply to scripts:
- compilation directory can be absolute or relative
- filename can be absolute, relative, or basename
- Paths to include files can be relative to compilation directory
or including file in some cases.
As said, I'll come back to this patch in a couple of days; let's see if
anyone else has a preference.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-11-25 19:11 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-16 19:36 Andrew STUBBS
2005-11-17 0:04 ` Eli Zaretskii
2005-11-17 12:41 ` Andrew STUBBS
2005-11-17 19:42 ` Eli Zaretskii
2005-11-18 13:23 ` Andrew STUBBS
2005-11-18 14:53 ` Eli Zaretskii
2005-11-18 15:54 ` Andrew STUBBS
2005-11-25 18:02 ` Andrew STUBBS
2005-11-25 18:12 ` Daniel Jacobowitz
2005-11-25 18:33 ` Andrew STUBBS
2005-11-25 18:39 ` Daniel Jacobowitz
2005-11-25 20:12 ` Andrew STUBBS
2005-11-25 21:26 ` Daniel Jacobowitz [this message]
2005-11-25 22:33 ` Eli Zaretskii
2005-11-28 19:34 ` Andrew STUBBS
2005-11-25 21:56 ` Eli Zaretskii
2005-11-25 21:43 ` Eli Zaretskii
2006-01-12 0:09 ` Andrew STUBBS
2006-01-22 20:40 ` Daniel Jacobowitz
2006-01-23 16:29 ` Andrew STUBBS
2006-01-23 17:41 ` Andrew STUBBS
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=20051125191116.GH736@nevyn.them.org \
--to=drow@false.org \
--cc=andrew.stubbs@st.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@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