We will add variants of these to support CHERI so bootstrap the manpages
from section 3.
Effort: CHERI upstreaming
Sponsored by: Innovate UK
Details
Details
Diff Detail
Diff Detail
- Repository
- rG FreeBSD src repository
- Lint
Lint Not Applicable - Unit
Tests Not Applicable
Event Timeline
Comment Actions
This looks fine, other than the 'string' choice. But maybe that's always been there. Maybe it's the standard jargon, but I thought I'd flag it.
| share/man/man9/bcopy.9 | ||
|---|---|---|
| 47 | "string" here and below? Is that something that you added for cheri, or is that legacy language. And if it's old, is there a better term? | |
| share/man/man9/bcopy.9 | ||
|---|---|---|
| 47 | This is a copy the text in bcopy.3 Glancing at memcpy in POSIX they use "object" instead of string and that would be better. | |
| share/man/man9/bcopy.9 | ||
|---|---|---|
| 47 | It comes from bcopy(3). I recall a similar discussion when I was working on documenting memcpy & overlapping objects (although I can't find it now). We could echo "byte string" (from .Nd) or maybe "object" | |
| share/man/man9/bcopy.9 | ||
|---|---|---|
| 47 | We could update the text in the section 3 pages as well | |
Comment Actions
Created D57680 to follow POSIX/C's lead and stop talking about strings in mem* functions.