From: Tom Tromey <tom@tromey.com>
To: Simon Farre via Gdb-patches <gdb-patches@sourceware.org>
Cc: Tom Tromey <tom@tromey.com>, Simon Farre <simon.farre.cx@gmail.com>
Subject: Re: [PATCH v1] gdb/DAP - Add completionsRequest
Date: Thu, 06 Jul 2023 09:16:03 -0600 [thread overview]
Message-ID: <87mt09ul3g.fsf@tromey.com> (raw)
In-Reply-To: <79d036ac-81f5-ee9b-233c-0b2f6f5a0f11@gmail.com> (Simon Farre via Gdb-patches's message of "Wed, 5 Jul 2023 16:02:02 +0200")
>>>>> "Simon" == Simon Farre via Gdb-patches <gdb-patches@sourceware.org> writes:
>> Since 'line' isn't used, I think it can just be removed here and also
>> from 'completions' itself, as it is optional anyway.
Simon> Right, I added it to make it look 1-to-1 with the DAP spec, _even
Simon> though_ we don't actually use them in GDB,
Simon> as I find this approach less confusing - if a GDB contributor (or
Simon> user) were to look up the signature, then look at the DAP spec
Simon> and not see the same things. But I'll remove the things that doesn't
Simon> make sense, as it were, in GDB-land in the next patch.
For the DAP side (the @request) this is arguable but also fine.
I personally think it's clearer to only name parameters that are
actually used, but if you want to do it that way, I'll approve it.
On the gdb side (@in_gdb_thread) I think it's better to only accept
things that are actually used. It's also arguably better here to do any
needed pre-processing in the DAP thread.
thanks,
Tom
prev parent reply other threads:[~2023-07-06 15:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 16:26 Simon Farre
2023-06-29 8:33 ` Lancelot SIX
2023-06-29 12:01 ` Simon Farre
2023-07-03 19:11 ` Tom Tromey
2023-07-05 14:02 ` Simon Farre
2023-07-06 15:16 ` Tom Tromey [this message]
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=87mt09ul3g.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.farre.cx@gmail.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).