From: Tom Tromey <tromey@redhat.com>
To: Phil Muldoon <pmuldoon@redhat.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
gdb-patches ml <gdb-patches@sourceware.org>
Subject: Re: [patch][python] Add symbol, symbol table and frame block support to GDB API
Date: Tue, 23 Feb 2010 23:05:00 -0000 [thread overview]
Message-ID: <m3zl2zwo1n.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20100219141457.GB2602@localhost.localdomain> (Phil Muldoon's message of "Fri, 19 Feb 2010 14:14:57 +0000")
>>>>> "Phil" == Phil Muldoon <pmuldoon@redhat.com> writes:
Tom> I think this could use a NEWS entry. I suggest waiting until my earlier
Tom> patch is approved, then adding items to that block... assuming your
Tom> patch goes in before 7.1. Otherwise, add a new Python block in the
Tom> post-7.1 changes.
Phil> I included one in the patch I sent. Here is the hunk:
Thanks, I must have missed it. Sorry about that.
Phil> This hunk puts it in the 7.1 release section. I'll move it when we
Phil> figure out what release it will be in (as of today, looks like 7.2).
Yeah, 7.2 now.
Phil> I ended up just reusing the FRAPY_REQUIRE_VALID code that is in
Phil> py-frame.c.
That code is bogus too, but I didn't want to burden you with this, at
least not for this patch ;).
Phil> +static PyObject *
Phil> +sympy_str (PyObject *self)
[...]
Phil> + s = xstrprintf ("symbol for %s",
Phil> + SYMBOL_PRINT_NAME (symbol));
Tom> Why not just have this be SYMBOL_PRINT_NAME?
Tom> I forgot the difference between the various python to-string methods.
Tom> Maybe this one is supposed to be more verbose? Let me know.
Phil> One of the tricky things I've found in merging work is I'm often not
Phil> the original author of that work.
Totally understood. This is all my fault or Thiago's :)
Phil> And my understanding of Python's "print object"
Phil> -> string is more for human consumption that for comparison or
Phil> assingment. That being said, I've no strong feelings on it. I did not
Phil> change it in this patch. If you want it changed, I'll happily do it.
Yes, I think we should change it so that "print foo" or "str(foo)"
yields the "most natural" name.
In this case it is just the print name.
Phil> + s = xstrprintf ("symbol table for %s",
Phil> + symtab->filename);
Tom> Also as above.
Phil> I'm not sure what this means, is it referring to the sympy_str
Phil> comment?
Yeah, sorry, do like sympy_str. In this case I think it should just
return the filename.
Phil> + s = xstrprintf ("symbol and line for %s, line %d", filename,
Phil> + sal->line);
Tom>
Phil> Ditto, sympy_str comment.
I am not sure what is nicest to return here; it is probably fine to
leave it as-is for the time being.
thanks,
Tom
next prev parent reply other threads:[~2010-02-23 23:05 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-01 13:42 Phil Muldoon
2010-02-01 20:54 ` Eli Zaretskii
2010-02-02 10:24 ` Phil Muldoon
2010-02-02 20:14 ` Eli Zaretskii
2010-02-03 20:55 ` Phil Muldoon
2010-02-05 10:53 ` Phil Muldoon
2010-02-05 18:06 ` Eli Zaretskii
2010-02-05 11:05 ` Eli Zaretskii
2010-02-04 23:25 ` Tom Tromey
2010-02-15 15:15 ` Phil Muldoon
2010-02-15 18:45 ` Eli Zaretskii
2010-02-15 23:39 ` Phil Muldoon
2010-02-16 4:12 ` Eli Zaretskii
2010-02-18 2:50 ` Tom Tromey
2010-02-19 14:15 ` Phil Muldoon
2010-02-19 14:28 ` Eli Zaretskii
2010-02-19 15:13 ` Phil Muldoon
2010-02-23 23:05 ` Tom Tromey [this message]
2010-02-24 16:58 ` Phil Muldoon
2010-02-24 17:22 ` Tom Tromey
2010-02-24 21:49 ` Phil Muldoon
2010-02-24 18:43 ` Eli Zaretskii
2010-02-23 23:09 ` 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=m3zl2zwo1n.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=pmuldoon@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