Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Michael Elizabeth Chastain <mec.gnu@mindspring.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfc/testsuite] editor.exp: new test script for "edit" command
Date: Fri, 23 Jul 2004 14:46:00 -0000	[thread overview]
Message-ID: <20040723144524.GA10859@nevyn.them.org> (raw)
In-Reply-To: <20040723064726.104F74B104@berman.michael-chastain.com>

On Fri, Jul 23, 2004 at 02:47:26AM -0400, Michael Chastain wrote:
> I'm particularly interested in whether this bit of TCL is okay:
> 
>   if { [file exists $actual_file] } then {
>     ...
>   } else {
>     ...
>   }
> 
> Should I use "file exists ..." or "remote_file build exists ..." here?
> 
> This is just RFC so far.  I need to understand the remote issue,
> and I suspect that I'm going to need a lot of "remote_file ..."
> stuff to create various files on the build system and manipulate
> them there.

Two things:
  - DejaGNU assumes that "build" is where tests are being run.
    There's never a need to use remote_file build.  Sometimes
    it is good for consistency, but see the next point.
  - GDB's testsuite assumes that host and build are the same.
    So I don't know if the consistency is worth it unless someone
    cares about separating them.


-- 
Daniel Jacobowitz


  reply	other threads:[~2004-07-23 14:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-23  6:46 Michael Elizabeth Chastain
2004-07-23 14:46 ` Daniel Jacobowitz [this message]
2004-07-24 23:59   ` Michael Chastain

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=20040723144524.GA10859@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mec.gnu@mindspring.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