From: Eli Zaretskii <eliz@gnu.org>
To: Thiago Jung Bauermann <bauerman@br.ibm.com>
Cc: drow@false.org, tromey@redhat.com, gdb-patches@sourceware.org
Subject: Re: [rfa][testsuite] Consolidade Python test functions in lib/gdb.exp.
Date: Wed, 20 May 2009 17:22:00 -0000 [thread overview]
Message-ID: <83fxezpu3m.fsf@gnu.org> (raw)
In-Reply-To: <1242832233.6644.2.camel@hactar>
> From: Thiago Jung Bauermann <bauerman@br.ibm.com>
> Cc: Eli Zaretskii <eliz@gnu.org>, tromey@redhat.com,
> gdb-patches@sourceware.org
> Date: Wed, 20 May 2009 12:10:33 -0300
>
> Ah, I didn't think of python-frame.c. It didn't exist when I did this
> back then. :-(
There are also value.c and utils.c.
> The right solution then is to make them not share a namespace.
Alternatively, we could use the following band-aid:
python-cmd.c -> pycmd.c
python-frame.c -> pyframe.c
python-function.c -> pyfunction.c
python-internal.h -> pyinternal.h
python-utils.c -> pyutils.c
python-value.c -> pyvalue.c
python.c -> python.c
python.h -> python.h
WDYT?
next prev parent reply other threads:[~2009-05-20 17:22 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-19 15:21 Thiago Jung Bauermann
2009-04-20 17:13 ` Tom Tromey
2009-04-20 17:23 ` Daniel Jacobowitz
2009-05-18 4:38 ` Thiago Jung Bauermann
2009-05-18 18:11 ` Eli Zaretskii
2009-05-19 14:50 ` Thiago Jung Bauermann
2009-05-19 14:59 ` Daniel Jacobowitz
2009-05-19 19:22 ` Eli Zaretskii
2009-05-19 22:21 ` Thiago Jung Bauermann
2009-05-20 3:11 ` Eli Zaretskii
2009-05-20 3:26 ` Thiago Jung Bauermann
2009-05-20 3:39 ` Daniel Jacobowitz
2009-05-20 13:18 ` Thiago Jung Bauermann
2009-05-20 14:59 ` Daniel Jacobowitz
2009-05-20 15:10 ` Thiago Jung Bauermann
2009-05-20 17:22 ` Eli Zaretskii [this message]
2009-05-20 19:39 ` Thiago Jung Bauermann
2009-05-20 20:00 ` Eli Zaretskii
2009-05-20 20:49 ` Thiago Jung Bauermann
2009-05-20 23:11 ` Joel Brobecker
2009-05-31 22:26 ` Thiago Jung Bauermann
2009-05-31 22:37 ` Thiago Jung Bauermann
2009-06-04 18:03 ` Tom Tromey
2009-05-28 0: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=83fxezpu3m.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=bauerman@br.ibm.com \
--cc=drow@false.org \
--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