Re:Considering C99 for Curl
by torstenvl on Tuesday November 22, 2022 @11:24AM
(#33707490)
The issue is that strncpy() isn't a str___() function, despite its name. It's a 0x00-padded memcpy.
[ Parent
| on HN ]
But it's not an str* function, it's an strn* function. And most (though not all, that would be too easy) work on fixed-size (hence the n) nul-padded strings.
No. It isn't. It has absolutely nothing to do with strings. There is no such thing as a fixed-sized string in C. "A string is a contiguous sequence of characters terminated by and including the first null character." § 7.1.1.
Calling your bespoke byte-sequence data structure a "string" is inaccurate and viewing strncpy() as a string function is erroneous and will lead to buffer overflows.
Have you considered giving reading comprehension a try?
Fixed-size strings are strings, just not nul-terminated strings. So are length-prefixed (“pascal”) strings.
Strncpy does not work with nul-terminated strings as I noted. If you’re working with fixed-size nul-padded strings however it’s the correct function to use.
> Have you considered giving reading comprehension a try?
Don't do this.
Then don’t demand it by wilfully misunderstanding comments in order to “well actually” them.
The output side of strncpy() might not be a str___() function, but AFAICS the input side of strncpy() is clearly a str___() function, since it stops reading (but not writing) at the first NUL byte.
It’s incidental more than purposeful, though it does have its use as a conversion function: with a nul-padded field, why would you keep copying once you’ve hit the first nul? You can just set from an immediate without the need to read from memory.