RE: strncasecmp

2020-04-11 Thread zeurkous
"Stuart Longland" wrote: > On 12/4/20 11:39 am, zeurk...@volny.cz wrote: >> "Stuart Longland" wrote: >>> On 11/4/20 2:30 am, zeurk...@volny.cz wrote: https://doomwiki.org/wiki/Absurd texture name in error message >> >> No, what I wrote is: >> >>> 'https://doomwiki.org/wiki/Absurd texture

Re: strncasecmp

2020-04-11 Thread Edgar Pettijohn
On 4/11/20 8:47 PM, Stuart Longland wrote: On 12/4/20 11:39 am, zeurk...@volny.cz wrote: "Stuart Longland" wrote: On 11/4/20 2:30 am, zeurk...@volny.cz wrote: https://doomwiki.org/wiki/Absurd texture name in error message No, what I wrote is: 'https://doomwiki.org/wiki/Absurd texture

Re: strncasecmp

2020-04-11 Thread Stuart Longland
On 12/4/20 11:39 am, zeurk...@volny.cz wrote: > "Stuart Longland" wrote: >> On 11/4/20 2:30 am, zeurk...@volny.cz wrote: >>> https://doomwiki.org/wiki/Absurd texture name in error message > > No, what I wrote is: > >> 'https://doomwiki.org/wiki/Absurd texture name in error message' > > World

RE: strncasecmp

2020-04-11 Thread zeurkous
"Stuart Longland" wrote: > On 11/4/20 2:30 am, zeurk...@volny.cz wrote: >> https://doomwiki.org/wiki/Absurd texture name in error message No, what I wrote is: > 'https://doomwiki.org/wiki/Absurd texture name in error message' World of difference. To a UNIX guy. >

Re: strncasecmp

2020-04-11 Thread Stuart Longland
On 11/4/20 2:30 am, zeurk...@volny.cz wrote: > https://doomwiki.org/wiki/Absurd texture name in error message https://doomwiki.org/wiki/Absurd%20texture%20name%20in%20error%20message Seems some people don't understand URIs… -- Stuart Longland (aka Redhatter, VK4MSL) I haven't lost my mind...

RE: strncasecmp

2020-04-10 Thread zeurkous
Haai, > From the man page: > > """"" > These functions compare the NUL-terminated strings s1 and s2 and > return an [...]. > > strncasecmp() and strncasecmp_l() compare at most len characters. > """"" > > Why

RE: strncasecmp

2020-04-10 Thread zeurkous
"Roderick" wrote: > > On Fri, 10 Apr 2020, Theo de Raadt wrote: > >> Because either string could be shorter than len. > > Thanks. I get it. :) My non-strings do not have a '\0' in the > first len bytes and I need a case insensitive comparison. > Of cour

Re: strncasecmp

2020-04-10 Thread Roderick
On Fri, 10 Apr 2020, Theo de Raadt wrote: Because either string could be shorter than len. Thanks. I get it. :) My non-strings do not have a '\0' in the first len bytes and I need a case insensitive comparison. Of course I could ignore strncasecmp and use tolower() to write the trivial

RE: strncasecmp

2020-04-10 Thread zeurkous
theo wrote: > Because either string could be shorter than len. > > strncasecmp() and strncasecmp_l() compare at most len characters. > ^^^ > > "NUL-terminated string" is firmly explaining to people that in C, > a string is only a string if it ends in a NU

Re: strncasecmp

2020-04-10 Thread Theo de Raadt
Because either string could be shorter than len. strncasecmp() and strncasecmp_l() compare at most len characters. ^^^ "NUL-terminated string" is firmly explaining to people that in C, a string is only a string if it ends in a NUL

strncasecmp

2020-04-10 Thread Roderick
From the man page: """"" These functions compare the NUL-terminated strings s1 and s2 and return an [...]. strncasecmp() and strncasecmp_l() compare at most len characters. """"" Why NULL-terminated when comparing at most len characters?! Rod.