From: Eli Zaretskii <eliz@gnu.org>
To: Andrew Burgess <aburgess@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 05/10] gdb/python: add some additional methods to gdb.PendingFrame
Date: Thu, 16 Mar 2023 16:46:57 +0200 [thread overview]
Message-ID: <833564rbxa.fsf@gnu.org> (raw)
In-Reply-To: <878rfwg481.fsf@redhat.com> (message from Andrew Burgess on Thu, 16 Mar 2023 14:28:46 +0000)
> From: Andrew Burgess <aburgess@redhat.com>
> Cc: gdb-patches@sourceware.org
> Date: Thu, 16 Mar 2023 14:28:46 +0000
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> >> + - gdb.PendingFrame.find_sal(): Return a gdb.Symtab_and_line
> >> >> + object for the current location within the pending frame, or
> >> >> + None.
> >> >> + - gdb.PendingFrame.block(): Return a gdb.Block for the current
> >> >> + pending frame, or None.
> >> >> + - gdb.PendingFrame.function(): Return a gdb.Symbol for the
> >> >> + current pending frame, or None.
> >> >
> >> > Btw, why do you follow each method name with a "()"? That looks like
> >> > a call with no arguments, which is not what you mean, right?
> >>
> >> I did indeed mean a call with no arguments. These would be used like
> >> this:
> >>
> >> class TestUnwinder(Unwinder):
> >> def __init__(self):
> >> super().__init__("Unwinder_Name")
> >>
> >> def __call__(self, pending_frame):
> >> is_valid = pending_frame.is_valid()
> >> name = pending_frame.name()
> >> pc = pending_frame.pc()
> >> language = pending_frame.language()
> >> sal = pending_frame.find_sal()
> >> block = pending_frame.block()
> >> function = pending_frame.function()
> >
> > That's not my point. AFAIU, the text on which I commented documents
> > the methods and what each one of them does. Then the "()" has no
> > place there, since you are naming the methods, not showing how to call
> > them. Right?
>
> I like to think we're documenting how to use the API, which includes how
> to call them.
That's true in Texinfo, but my comment was about NEWS.
> @defvar ClassName.Attribute
> Contains a value.
> @end defvar
>
> @defun ClassName.NoArgsMethod()
> Does stuff.
> @end defun
>
> @defun ClassName.TakesArgs(@var{arg1}, @var{arg2})
> Does other stuff.
> @end defun
>
> If I've understood your correctly (sorry if I have not), then you are
> suggesting dropping the '()' from the 'NoArgsMethod' case.
Not in Texinfo, no. In Texinfo, we do show the signature when we
document a function or a method. But NEWS is mostly free-form text,
and in free-form text there's no reason to append a signature whenever
you mention the name of a function or a method.
next prev parent reply other threads:[~2023-03-16 14:47 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-10 14:55 [PATCH 00/10] Improvements & Cleanup For Python Unwinder API Andrew Burgess
2023-03-10 14:55 ` [PATCH 01/10] gdb/doc: spring clean the Python unwinders documentation Andrew Burgess
2023-03-10 15:24 ` Eli Zaretskii
2023-03-14 9:27 ` Andrew Burgess
2023-03-14 12:56 ` Eli Zaretskii
2023-03-16 14:30 ` Andrew Burgess
2023-03-10 14:55 ` [PATCH 02/10] gdb/python: make the gdb.unwinder.Unwinder class more robust Andrew Burgess
2023-03-10 15:32 ` Eli Zaretskii
2023-03-14 10:06 ` Andrew Burgess
2023-03-14 12:57 ` Eli Zaretskii
2023-03-31 2:15 ` Simon Marchi
2023-04-03 10:02 ` Andrew Burgess
2023-03-10 14:55 ` [PATCH 03/10] gdb/python: remove unneeded nullptr check in frapy_block Andrew Burgess
2023-03-10 14:55 ` [PATCH 04/10] gdb/python: add PENDING_FRAMEPY_REQUIRE_VALID macro in py-unwind.c Andrew Burgess
2023-03-10 14:55 ` [PATCH 05/10] gdb/python: add some additional methods to gdb.PendingFrame Andrew Burgess
2023-03-10 15:42 ` Eli Zaretskii
2023-03-14 10:18 ` Andrew Burgess
2023-03-14 12:59 ` Eli Zaretskii
2023-03-16 14:28 ` Andrew Burgess
2023-03-16 14:46 ` Eli Zaretskii [this message]
2023-03-16 17:26 ` Andrew Burgess
2023-03-16 19:54 ` Eli Zaretskii
2023-03-10 14:55 ` [PATCH 06/10] gdb/python: add __repr__ for PendingFrame and UnwindInfo Andrew Burgess
2023-03-10 14:55 ` [PATCH 07/10] gdb/python: remove Py_TPFLAGS_BASETYPE from gdb.UnwindInfo Andrew Burgess
2023-03-10 14:55 ` [PATCH 08/10] gdb: have value_as_address call unpack_pointer Andrew Burgess
2023-03-10 15:28 ` Tom Tromey
2023-03-10 22:08 ` Andrew Burgess
2023-03-10 14:55 ` [PATCH 09/10] gdb/python: Allow gdb.UnwindInfo to be created with non gdb.Value args Andrew Burgess
2023-03-10 15:34 ` Tom Tromey
2023-03-10 22:16 ` Andrew Burgess
2023-03-11 14:47 ` Tom Tromey
2023-03-10 15:38 ` Eli Zaretskii
2023-03-10 14:55 ` [PATCH 10/10] gdb/python: Add new gdb.unwinder.FrameId class Andrew Burgess
2023-03-10 15:36 ` Eli Zaretskii
2023-03-14 10:58 ` Andrew Burgess
2023-03-14 13:00 ` Eli Zaretskii
2023-03-29 16:27 ` [PATCH 00/10] Improvements & Cleanup For Python Unwinder API 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=833564rbxa.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=aburgess@redhat.com \
--cc=gdb-patches@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).