This is the mail archive of the
mailing list for the glibc project.
Re: strtok behaviour when uninitialized
On Mon, Feb 19, 2018 at 06:41:20PM +0100, Andreas Schwab wrote:
> On Feb 19 2018, Ondřej Bílka <email@example.com> wrote:
> > It is function that's broken by design, even without threads. If one
> > calls any library function while strtok is going and then in later
> > version of library one decides to also use strtok it will break previous
> > one.
> All standard library functions are required to behave as if they never
> call strtok.
I was talking about third party libraries.