From: "Ludovic Courtès" <ludo@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Doug Evans <xdje42@gmail.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 1/2] guile: Add support for Guile 2.2.
Date: Sat, 13 Jun 2020 17:04:57 +0200 [thread overview]
Message-ID: <87wo4bypk6.fsf@gnu.org> (raw)
In-Reply-To: <83k10b4g8b.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 13 Jun 2020 09:44:36 +0300")
Hi,
In the meantime I found that Doug had already done that work in 2018:
https://sourceware.org/bugzilla/show_bug.cgi?id=21104#c8
Too bad I didn’t notice earlier. I’ll check if there are significant
differences between the two.
Eli Zaretskii <eliz@gnu.org> skribis:
>> These four functions are not used in tests, in documented examples, nor
>> in Guile’s own GDB plugin.
>>
>> ‘setvbuf’ is not entirely a drop-in replacement because: (1) it doesn’t
>> allow you to query a port’s buffer size, only to change it, and (2) it
>> doesn’t distinguish between the read and write buffers. Consequently,
>> these functions cannot be implemented on 2.2/3.0, or at least not
>> easily.
>>
>> Since they are unused, and I can’t see a valid use case for those over
>> ‘setvbuf’, I chose to remove them from the manual as a way to deprecate
>> them.
>>
>> WDYT?
>
> So what is the plan wrt GDB accessing memory of the inferior via
> Guile? Specifically, which parts of the features described in "Memory
> Ports in Guile" in the manual will continue be supported with Guile 2.2
> and later? can we make at least the accessors work with those newer
> versions of Guile?
Yes, everything remains supported, it’s just setting read/write
buffering size in that way that is unsupported.
In most cases, I suspect one just wants an unbuffered memory port
anyway.
> In any case, I don't like the method of deprecating features by
> removing their documentation. I think we should say explicitly in
> that section which methods are deprecated and why. The fact that they
> are deprecated should also be in NEWS. This all assumes that other
> GDB developers agree that they are not needed; I don't have enough
> relevant experience to have an opinion. Maybe Doug (CC'ed) could
> chime in.
Yes, I think we should mention it in ‘NEWS’.
> I also think that Guile should provide proper replacements for the
> functionality you mentioned, because evidently at least GDB thought
> they could be put to good use. But this is outside of the scope of
> GDB maintenance, something for the Guile developers to consider.
Right. For I/O ports in general, I don’t think this functionality would
be very useful. (Even for GDB memory ports, I think ‘setvbuf’ is
enough.)
>> > Also, does any of this need to be called out in NEWS?
>>
>> Oh sure. Should that go in a separate commit or in the same?
>
> The same is better.
Sounds good.
Thanks,
Ludo’.
next prev parent reply other threads:[~2020-06-13 15:05 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-12 13:27 [PATCH 0/2] Add support for Guile 3.0 and 2.2 Ludovic Courtès
2020-06-12 13:27 ` [PATCH 1/2] guile: Add support for Guile 2.2 Ludovic Courtès
2020-06-12 13:50 ` Eli Zaretskii
2020-06-12 14:04 ` Ludovic Courtès
2020-06-13 6:44 ` Eli Zaretskii
2020-06-13 15:04 ` Ludovic Courtès [this message]
2020-06-15 15:14 ` [PATCH v2 0/2] Add support for Guile 3.0 and 2.2 Ludovic Courtès
2020-06-15 15:14 ` [PATCH v2 1/2] guile: Add support for Guile 2.2 Ludovic Courtès
2020-06-15 17:00 ` Eli Zaretskii
2020-06-18 20:31 ` Tom Tromey
2020-06-19 6:08 ` Eli Zaretskii
2020-06-19 7:37 ` Ludovic Courtès
2020-06-26 8:13 ` [PATCH v3 0/2] Add support for Guile 3.0 and 2.2 Ludovic Courtès
2020-06-26 8:13 ` [PATCH v3 1/2] guile: Add support for Guile 2.2 Ludovic Courtès
2020-06-26 10:23 ` Eli Zaretskii
2020-06-28 14:20 ` Ludovic Courtès
2020-06-28 14:25 ` [PATCH v4 " Ludovic Courtès
2020-06-28 16:40 ` Eli Zaretskii
2020-07-03 0:31 ` Simon Marchi
2020-07-03 7:06 ` Ludovic Courtès
2020-07-18 19:00 ` Joel Brobecker
2020-07-19 15:45 ` Simon Marchi
2020-07-20 8:05 ` Ludovic Courtès
2020-07-20 15:01 ` Simon Marchi
2020-07-21 21:10 ` Ludovic Courtès
2020-06-28 14:25 ` [PATCH v4 2/2] guile: Add support for Guile 3.0 Ludovic Courtès
2020-06-28 16:38 ` [PATCH v3 1/2] guile: Add support for Guile 2.2 Eli Zaretskii
2020-06-28 16:51 ` Ludovic Courtès
2020-07-02 12:57 ` [PING] Add support for Guile 2.2/3.0 Ludovic Courtès
2020-07-13 15:36 ` Tom Tromey
2020-06-26 8:13 ` [PATCH v3 2/2] guile: Add support for Guile 3.0 Ludovic Courtès
2020-06-26 10:13 ` Eli Zaretskii
2020-06-15 15:14 ` [PATCH v2 " Ludovic Courtès
2020-06-12 14:14 ` [PATCH 1/2] guile: Add support for Guile 2.2 Tom de Vries
2020-06-12 14:36 ` Ludovic Courtès
2020-06-12 13:27 ` [PATCH 2/2] guile: Add support for Guile 3.0 Ludovic Courtès
2020-06-15 15:02 ` Tom Tromey
2020-06-15 15:17 ` Ludovic Courtès
2020-06-17 16:58 ` Ludovic Courtès
2020-06-17 17:21 ` Eli Zaretskii
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=87wo4bypk6.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=xdje42@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).