From: Florian Weimer <fweimer@redhat.com>
To: Jayakrishna Vadayath via Libc-alpha <libc-alpha@sourceware.org>
Cc: Jayakrishna Vadayath <jvadayat@asu.edu>
Subject: Re: Implementation of strtok
Date: Fri, 02 Jun 2023 07:40:42 +0200 [thread overview]
Message-ID: <87edmupgkl.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <CAFrQ_576eJNts7cky1U7EpWK2VOuBrXj=+Av2j3QbMsdMWJ3YA@mail.gmail.com> (Jayakrishna Vadayath via Libc-alpha's message of "Thu, 1 Jun 2023 22:22:29 -0700")
* Jayakrishna Vadayath via Libc-alpha:
> According to the documentation of the strchr and strtok functions, it would
> appear that (1) will never be executed.
I looked at various descriptions of strtok, and they are pretty clear
that the implemented behavior is required. Where did you find
conflicting information?
Thanks,
Florian
next prev parent reply other threads:[~2023-06-02 5:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-02 5:22 Jayakrishna Vadayath
2023-06-02 5:40 ` Florian Weimer [this message]
2023-06-02 5:52 ` Jayakrishna Vadayath
2023-06-02 6:05 ` Florian Weimer
2023-06-02 6:17 ` Jayakrishna Vadayath
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=87edmupgkl.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=jvadayat@asu.edu \
--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).