From: Tom Tromey <tromey@adacore.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Tom Tromey <tromey@adacore.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 2/3] Implement real literal extension for Ada
Date: Mon, 07 Mar 2022 08:28:09 -0700 [thread overview]
Message-ID: <877d95rddi.fsf@tromey.com> (raw)
In-Reply-To: <8335k1lh9e.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 01 Mar 2022 19:22:37 +0200")
Eli> "Exact byte contents" is not the best way to describe this
Eli> specification of a value. If no better idea emerges, how about using
Eli> the same description as you used in the manual?
I did this, thanks.
Tom
next prev parent reply other threads:[~2022-03-07 15:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 17:00 [PATCH 0/3] Floating-point literal syntax " Tom Tromey
2022-03-01 17:00 ` [PATCH 1/3] Fix Ada integer literals with exponents Tom Tromey
2022-03-01 17:00 ` [PATCH 2/3] Implement real literal extension for Ada Tom Tromey
2022-03-01 17:22 ` Eli Zaretskii
2022-03-07 15:28 ` Tom Tromey [this message]
2022-03-16 14:33 ` Luis Machado
2022-03-18 18:05 ` Tom Tromey
2022-03-21 9:28 ` Luis Machado
2022-03-29 8:13 ` Luis Machado
2022-03-01 17:00 ` [PATCH 3/3] Fix bug in ada_print_floating Tom Tromey
2022-03-07 15:28 ` [PATCH 0/3] Floating-point literal syntax extension for Ada 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=877d95rddi.fsf@tromey.com \
--to=tromey@adacore.com \
--cc=eliz@gnu.org \
--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).