public inbox for newlib@sourceware.org
 help / color / mirror / Atom feed
From: Corinna Vinschen <vinschen@redhat.com>
To: Aditya Upadhyay <aadit0402@gmail.com>
Cc: newlib@sourceware.org
Subject: Re: Importing inttypes methods
Date: Wed, 26 Jul 2017 11:08:00 -0000	[thread overview]
Message-ID: <20170726110849.GG14419@calimero.vinschen.de> (raw)
In-Reply-To: <CAMZxAxdZCKzgxRSSLbfO9p9Orqor7wv2wKgpezXeXyiHShnO3g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1121 bytes --]

On Jul 26 01:20, Aditya Upadhyay wrote:
> Hello All,
> 
> I have ported the inttypes methods from freeBSD. I have made all the
> possible changes whatever my mentors suggested me. I am requesting you
> to please review the same. Is this ok for master ?

The patches apply and build.  This looks 99% good now, thank you.

Just one last minor problem, which is my fault, not yours:

You named the reentrant functions _strtoimax_r, _wcstoumax_r, etc.,
which is basically right.

However, the *other*, equivalent reentrant, locale-specific functions
for other datatypes are all named with a trailing l: _strtol_l,
_wcstoull_l, etc.  In retrospect, this wasn't the brightest idea,
but the API has been exported this way, so I'm reluctant to change
it after the fact.

Would you mind to call your new functions with trailing 'l' rather
than 'r', too, to use the same naming convention, please?

Oh, btw., please make sure the patches have no trailing whitespace.
That's not really a problem, but `git am' complains about them.


Thanks,
Corinna

-- 
Corinna Vinschen
Cygwin Maintainer
Red Hat

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2017-07-26 11:08 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-25 19:51 Aditya Upadhyay
2017-07-26 11:08 ` Corinna Vinschen [this message]
2017-07-26 12:02   ` Sebastian Huber
2017-07-26 12:02   ` Aditya Upadhyay
2017-07-26 21:24     ` Aditya Upadhyay
2017-07-27 12:32       ` Corinna Vinschen
2017-07-27 14:00         ` Aditya Upadhyay
2017-07-28 10:43           ` Corinna Vinschen
2017-07-28 11:02             ` Aditya Upadhyay
2017-07-28 11:40               ` Gedare Bloom
2017-07-28 13:08                 ` Corinna Vinschen
2017-07-28 14:28                   ` Gedare Bloom
2017-07-28 18:29                     ` Corinna Vinschen
2017-07-29 12:40                       ` Gedare Bloom
2017-07-29 13:57                         ` Aditya Upadhyay
2017-07-30  8:46                           ` Aditya Upadhyay
2017-07-30 15:41                             ` Gedare Bloom
2017-07-31 10:08                               ` Corinna Vinschen
2017-08-01  8:31                                 ` Aditya Upadhyay
2017-08-01 12:10                                   ` Gedare Bloom
2017-07-28 18:24               ` Joel Sherrill

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=20170726110849.GG14419@calimero.vinschen.de \
    --to=vinschen@redhat.com \
    --cc=aadit0402@gmail.com \
    --cc=newlib@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).