From: Eli Zaretskii <eliz@gnu.org>
To: George Barrett <bob@bob131.so>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v3 3/3] Guile: add value-const-value
Date: Wed, 28 Apr 2021 19:39:49 +0300 [thread overview]
Message-ID: <8335vafjmy.fsf@gnu.org> (raw)
In-Reply-To: <q4on2w667ekxl9y0d3k2u83fqa9wdd54wfsifzo_ba6p9s/855.8@mail.bob131.so> (message from George Barrett via Gdb-patches on Thu, 29 Apr 2021 02:27:49 +1000)
> Date: Thu, 29 Apr 2021 02:27:49 +1000
> From: George Barrett via Gdb-patches <gdb-patches@sourceware.org>
> Cc: George Barrett <bob@bob131.so>
>
> The Guile API doesn't currently have an equivalent to the Python API's
> gdb.Value.const_value(). This commit adds a procedure with equivalent
> semantics to the Guile API.
>
> gdb/ChangeLog:
>
> 2021-04-29 George Barrett <bob@bob131.so>
>
> * guile/scm-value.c (gdbscm_value_const_value): Add
> implementation of value-const-value procedure.
> (value_functions): Add value-const-value procedure.
> * NEWS (Guile API): Note the addition of the new procedure.
>
> gdb/doc/ChangeLog:
>
> 2021-04-29 George Barrett <bob@bob131.so>
>
> * guile.texi (Values From Inferior In Guile): Add
> documentation for value-const-value.
>
> gdb/testsuite/ChangeLog:
>
> 2021-04-29 George Barrett <bob@bob131.so>
>
> * gdb.guile/scm-value.exp (test_value_in_inferior): Add test
> for value-const-value.
OK for the documentation parts.
Thanks.
next prev parent reply other threads:[~2021-04-28 16:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-28 16:27 [PATCH v3 0/3] Guile: add value-{reference,const}-value George Barrett
2021-04-28 16:27 ` [PATCH v3 1/3] Guile: improved rvalue reference support George Barrett
2021-04-28 16:38 ` Eli Zaretskii
2021-04-28 16:54 ` Andrew Burgess
2021-04-28 16:27 ` [PATCH v3 2/3] Guile: add {r,}value-reference-value George Barrett
2021-04-28 16:40 ` Eli Zaretskii
2021-04-28 16:59 ` Andrew Burgess
2021-04-28 17:11 ` George Barrett
2021-04-28 16:27 ` [PATCH v3 3/3] Guile: add value-const-value George Barrett
2021-04-28 16:39 ` Eli Zaretskii [this message]
2021-04-28 17:00 ` Andrew Burgess
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=8335vafjmy.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=bob@bob131.so \
--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).