public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Rical Jasan <ricaljasan@pacific.net>
To: Joseph Myers <joseph@codesourcery.com>
Cc: "Gabriel F. T. Gomes" <gftg@linux.vnet.ibm.com>,
	libc-alpha@sourceware.org
Subject: Re: [PATCH v5 1/3] Add strfromd, strfromf, and strfroml functions
Date: Wed, 05 Oct 2016 21:06:00 -0000	[thread overview]
Message-ID: <d16f5681-f2c2-59ce-e98e-1ce4b5f40952@pacific.net> (raw)
In-Reply-To: <alpine.DEB.2.20.1610051603120.1722@digraph.polyomino.org.uk>

On 10/05/2016 09:05 AM, Joseph Myers wrote:
> On Wed, 5 Oct 2016, Rical Jasan wrote:
> 
>>> +These functions have been introduced by ISO/IEC TS 18661-1.
>>
>> 20-years later it might be nice if this didn't sound like it just
>> happened.  Perhaps "were introduced", which gives it a solid,
>> future-proofing past tense feel?
> 
> I agree with that comment, but also hope that 20 years later we have 
> something like I suggested at the bottom of 
> <https://sourceware.org/ml/libc-alpha/2016-06/msg00039.html> replacing 
> such free-form text (although replacing the free-form text, which requires 
> going through the whole manual, would involve rather more work than moving 
> from @comment to appropriate macros, which would be an essentially 
> automated change).

I was going to make an off-hand comment about adding that kind of
machinery, but bit my tongue, feeling it to be a little out of scope for
this patch's review.  :)

I have that work on my to-do list, in case no one gets to it in 20
years, or before me, whichever is sooner...

Rical

  reply	other threads:[~2016-10-05 21:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-04 20:58 [PATCH v5 0/3] New strfrom functions Gabriel F. T. Gomes
2016-10-04 20:58 ` [PATCH v5 1/3] Add strfromd, strfromf, and strfroml functions Gabriel F. T. Gomes
2016-10-05  8:38   ` Rical Jasan
2016-10-05 12:07     ` Joseph Myers
2016-10-05 13:55       ` Gabriel F. T. Gomes
2016-10-05 16:05     ` Joseph Myers
2016-10-05 21:06       ` Rical Jasan [this message]
2016-10-04 20:58 ` [PATCH v5 3/3] Add tests for strfrom functions Gabriel F. T. Gomes
2016-10-04 20:58 ` [PATCH v5 2/3] Refactor strtod tests Gabriel F. T. Gomes

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=d16f5681-f2c2-59ce-e98e-1ce4b5f40952@pacific.net \
    --to=ricaljasan@pacific.net \
    --cc=gftg@linux.vnet.ibm.com \
    --cc=joseph@codesourcery.com \
    --cc=libc-alpha@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).