From: Eli Zaretskii <eliz@gnu.org>
To: Simon Marchi <simon.marchi@ericsson.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] python doc: Rework Breakpoint.__init__ doc
Date: Sat, 09 Dec 2017 08:22:00 -0000 [thread overview]
Message-ID: <83o9n8uxbc.fsf@gnu.org> (raw)
In-Reply-To: <52711e30-004e-3a2c-d77c-e409a1f66d9e@ericsson.com> (message from Simon Marchi on Fri, 8 Dec 2017 15:46:59 -0500)
> CC: <gdb-patches@sourceware.org>
> From: Simon Marchi <simon.marchi@ericsson.com>
> Date: Fri, 8 Dec 2017 15:46:59 -0500
>
> - don't use spec and function/line/label/source at the same time
> - you should choose (exclusively) one form (the one that uses spec) or
> the other (the one that uses function/line/label/source)
My question was about the 2nd form only: which of the keywords can or
cannot be used together, and what is the semantics of their
combinations? I suspect the rules are the same as with the CLI
command, so I think we should either tell that or add a
cross-reference to where that's described for CLI.
> However, showing two different constructors in the documentation is not technically
> accurate with how it is implemented in the Python-support code, because it is
> not possible to have two constructors with different signatures in Python.
That's okay, since the manual says "2 forms", not "2 constructors".
Right?
next prev parent reply other threads:[~2017-12-09 8:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-07 21:23 Simon Marchi
2017-12-08 14:12 ` Eli Zaretskii
2017-12-08 18:00 ` Simon Marchi
2017-12-08 19:45 ` Eli Zaretskii
2017-12-08 20:47 ` Simon Marchi
2017-12-09 8:22 ` Eli Zaretskii [this message]
2017-12-12 21:16 ` Simon Marchi
2017-12-13 3:35 ` Eli Zaretskii
2017-12-13 4:54 ` Simon Marchi
2017-12-13 16:07 ` Eli Zaretskii
2017-12-13 16:29 ` Simon Marchi
2017-12-08 18:22 ` [PATCH v2] " Simon Marchi
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=83o9n8uxbc.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@ericsson.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).