From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from eggs.gnu.org (eggs.gnu.org [209.51.188.92]) by sourceware.org (Postfix) with ESMTPS id DC5CA3858D20 for ; Tue, 1 Mar 2022 17:22:45 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org DC5CA3858D20 Received: from [2001:470:142:3::e] (port=40172 helo=fencepost.gnu.org) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nP6Cz-0005o9-9J; Tue, 01 Mar 2022 12:22:45 -0500 Received: from [87.69.77.57] (port=4705 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nP6Cy-0001NC-OC; Tue, 01 Mar 2022 12:22:45 -0500 Date: Tue, 01 Mar 2022 19:22:37 +0200 Message-Id: <8335k1lh9e.fsf@gnu.org> From: Eli Zaretskii To: Tom Tromey Cc: gdb-patches@sourceware.org In-Reply-To: <20220301170055.1520935-3-tromey@adacore.com> (message from Tom Tromey via Gdb-patches on Tue, 1 Mar 2022 10:00:54 -0700) Subject: Re: [PATCH 2/3] Implement real literal extension for Ada References: <20220301170055.1520935-1-tromey@adacore.com> <20220301170055.1520935-3-tromey@adacore.com> X-Spam-Status: No, score=1.5 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_BARRACUDACENTRAL, SPF_HELO_PASS, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.4 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Mar 2022 17:22:46 -0000 > Date: Tue, 1 Mar 2022 10:00:54 -0700 > From: Tom Tromey via Gdb-patches > Cc: Tom Tromey > > +* GDB's Ada parser now supports an extension for specifying the exact > + byte contents of a floating-point literal. This can be useful for "Exact byte contents" is not the best way to describe this specification of a value. If no better idea emerges, how about using the same description as you used in the manual? Otherwise, the documentation part is OK. Thanks.