[Bug 42042] strchr(3) and memchr(3) should explain behaviour when character 'c' is '\0'.

[bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r@public.gmane.org]

https://bugzilla.kernel.org/show_bug.cgi?id=42042





--- Comment #7 from Michael Kerrisk <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>  2012-04-23 20:36:56 ---
James,

Regarding memchr(), I'm not sure a change is warranted. memchr() is defined in
terms of 'bytes' and 'memory areas', rather than strings, so I'd have said it
would take an obtuse reading to consider that '\0' is interpreted specially
(whereas, as you say, one could be left doubtful about what strchr() does when
c is '\0'). 

I'd guess that this is also why POSIX and the FreeBSD man page make no
statement on this pont.

So, I'm inclined not to make a change.

Thanks,

Michael

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html