From: Pedro Alves <palves@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: FYI: fixlet for linux-dp.exp
Date: Thu, 26 Apr 2012 14:04:00 -0000 [thread overview]
Message-ID: <4F9955CD.5040106@redhat.com> (raw)
In-Reply-To: <8762cndijg.fsf@fleche.redhat.com>
On 04/25/2012 02:53 PM, Tom Tromey wrote:
> It would be nice if dejagnu made a new interpreter for each .exp file,
> so that variable name clashes couldn't happen...
I assume this would mean use "interp create". It's even on dejagnu's TODO file:
Last updated $Date: 2004/02/08 14:02:07 $
Bigger items
============
...
* Use a throw-away slave interpreter for running each test case.
I think the trouble would be globals that _are_ supposed to be persistent
across tests, like e.g., "portnum", or whatever other globals board
files can come up with. We'd need some common way to make
those "master interp" owned variables (through aliases or env vars?).
Alternatively, we could save/restore globals, but there's no globals
standard naming scheme in place to make that remotely sane.
--
Pedro Alves
next prev parent reply other threads:[~2012-04-26 14:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-25 14:39 Tom Tromey
2012-04-26 14:04 ` Pedro Alves [this message]
2012-04-26 14:34 ` Joel Brobecker
2012-04-26 14:43 ` Tom Tromey
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=4F9955CD.5040106@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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