From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <SRS0=z1kk=BW=redhat.com=fweimer@sourceware.org>
Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124])
	by sourceware.org (Postfix) with ESMTPS id 2C88E3858D1E
	for <libc-alpha@sourceware.org>; Fri,  2 Jun 2023 05:40:47 +0000 (GMT)
DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 2C88E3858D1E
Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=redhat.com
Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=redhat.com
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com;
	s=mimecast20190719; t=1685684446;
	h=from:from:reply-to:subject:subject:date:date:message-id:message-id:
	 to:to:cc:cc:mime-version:mime-version:content-type:content-type:
	 in-reply-to:in-reply-to:references:references;
	bh=nNW9ONLjBG2pNAcCqrldjS4uZwbwptL2af5Dz3OCsqA=;
	b=C/5lj+FzCLLse9ceuT/vlKUGYqcKUqRWtd882w+d1sAbLS1RYwVUl3VHje69ou/BtRz0Bp
	lSpbKlkiRK1WSq7uhWbs1jVEfpbh+nNNPwXSWE3ekTxqMU/rYfN08+vwKd/K0UE7Ejz5N5
	ffyit3bsK4Fa14nd+5qWcAVUonynzEw=
Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com
 [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS
 (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
 us-mta-378-nHkD702nMKmMZM60EaNjwg-1; Fri, 02 Jun 2023 01:40:45 -0400
X-MC-Unique: nHkD702nMKmMZM60EaNjwg-1
Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.rdu2.redhat.com [10.11.54.5])
	(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 571E6185A78E;
	Fri,  2 Jun 2023 05:40:45 +0000 (UTC)
Received: from oldenburg.str.redhat.com (unknown [10.2.16.20])
	by smtp.corp.redhat.com (Postfix) with ESMTPS id 8B8EA8162;
	Fri,  2 Jun 2023 05:40:44 +0000 (UTC)
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
References: <CAFrQ_576eJNts7cky1U7EpWK2VOuBrXj=+Av2j3QbMsdMWJ3YA@mail.gmail.com>
Date: Fri, 02 Jun 2023 07:40:42 +0200
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")
Message-ID: <87edmupgkl.fsf@oldenburg.str.redhat.com>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.2 (gnu/linux)
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 3.1 on 10.11.54.5
X-Mimecast-Spam-Score: 0
X-Mimecast-Originator: redhat.com
Content-Type: text/plain
X-Spam-Status: No, score=-4.6 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_NONE,TXREP,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org
List-Id: <libc-alpha.sourceware.org>

* 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