public inbox for newlib@sourceware.org
 help / color / mirror / Atom feed
From: Aditya Upadhyay <aadit0402@gmail.com>
To: Gedare Bloom <gedare@rtems.org>, newlib@sourceware.org
Subject: Re: Reentrant version of inttypes methods
Date: Sun, 23 Jul 2017 12:36:00 -0000	[thread overview]
Message-ID: <CAMZxAxc2Gg5HKkHLp4k_jYxXBnA3ft7VF4-MJBmxLgoJfsqOMQ@mail.gmail.com> (raw)
In-Reply-To: <CAC82fA2Mug1UQY525A-BWpoCmKpxt58jpaB8Or6hzpzi2aEHzg@mail.gmail.com>

Yes, I have seen many files which contains declaration of reentrant
version of methods like stdlib.h, string.h etc.. I am adding the
declaration of same in original inttypes.h header file. Also i have
gone through the newlib libc docs and have seen list of reentrant
function. Finally, i am having understanding of reentrancy.

Thanks & Regards,
Aditya Upadhyay

On Sun, Jul 23, 2017 at 5:42 PM, Gedare Bloom <gedare@rtems.org> wrote:
> I think the reentrant functions can be declared directly in inttypes.h
> as other headers do in libc/include. Put the _r (and _l) versions
> close to the declarations of the non-reentrant.
>
> On Sat, Jul 22, 2017 at 7:26 AM, Aditya Upadhyay <aadit0402@gmail.com> wrote:
>> Hello All,
>>
>> In FreeBSD, There is a _inttypes.h for reentrant version of inttypes
>> methods. So, Do i need to make reentrant version of inttypes.h ? It
>> seems there does not exist something like _inttypes.h stuff in newlib
>> or Do i have to add the declaration of strtoimax_l and _strtoimax_r in
>> stdlib.h file ? I think, There should be  _inttypes.h header file
>> support for reentrant version of inttypes method. Please correct me if
>> i am wrong.
>>
>>
>> Thanks & Regards,
>> Aditya Upadhyay

  reply	other threads:[~2017-07-23 12:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-22 11:26 Aditya Upadhyay
2017-07-23 12:12 ` Gedare Bloom
2017-07-23 12:36   ` Aditya Upadhyay [this message]
2017-07-24 12:40     ` Eric Blake

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=CAMZxAxc2Gg5HKkHLp4k_jYxXBnA3ft7VF4-MJBmxLgoJfsqOMQ@mail.gmail.com \
    --to=aadit0402@gmail.com \
    --cc=gedare@rtems.org \
    --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).