strtok behaviour when uninitialized

Andreas Schwab schwab@suse.de
Mon Feb 19 17:50:00 GMT 2018


On Feb 19 2018, Ondřej Bílka <neleai@seznam.cz> 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.

Andreas.

-- 
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."



More information about the Libc-alpha mailing list