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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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





--- Comment #7 from Michael Kerrisk <mtk.manpages@xxxxxxxxx>  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@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Kernel Documentation]     [Netdev]     [Linux Ethernet Bridging]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux