Re: [Bug-gnulib] strtok_r

[Paul Eggert]

Simon Josefsson <address@hidden> writes:

> * Is strchr the same as rawmemchr?

No, strchr (BUF, CH) stops when it finds either CH or a null byte.
rawmemchr (BUF, CH) stops only when it finds CH.

If CH is zero (which is the case here), the two functions are
equivalent, but presumably rawmemchr is faster.

> I didn't like rawmemchr.

Just as an aside, I didn't even know about rawmemchr until now.  But
it looks nice to me.  What don't you like about it?

> * Glibc doesn't seem to have restrict keywords in the *.c file.  Is
>   that a bug?  Is it sufficient to have them in *.h?

C99 isn't entirely clear on the subject.  I think the intent was that
it's sufficient to have them in *.h.  I wouldn't worry about it unless
we run across a (possibly pre-C99) compiler that complains about it,
or unless it turns into a real performance problem.