It is not immediately clear from the standard what strncmp (from string.h) int strncmp(const char *s1, const char *s2, size_t n); should return if its 3rd argument n is 0. According to the C17 sta...

For educational purposes (yes 42 yes) I'm rewriting strncmp and a classmate just came up to me asking why I was casting my returnvalues in such a way. My suggestion was to typecast first and derefe...

I became curious to understand the internals of how string comparison works in python when I was solving the following example algorithm problem: Given two strings, return the length of the long...

I have an array of 16 bytes that holds the name of an executable's segment. char segname[16]; If the segment name length is less than 16 bytes, then the rest is padded with null bytes. Otherwise...

Fortify indicates that this is an out of bounds read: if (strncmp("test string", "less than 32 char", 32) == 0) { ... } It says that the function reads data from outside the bounds of less than ...

Is it safe to put NULL pointer as parameter of strncmp if the third parameter is zero? I.e. an invocation like: strncmp(NULL, "foo", 0);

By my understanding, strcmp() (no 'n'), upon seeing a null character in either argument, immediately stops processing and returns a result. Therefore, if one of the arguments is known with 100% c...

The c/c++ strncmp signature is like the following: int strncmp ( const char * str1, const char * str2, size_t num ); My question is what's the return value if num is 0? How the standard says? Do...