On 27.01.2016 01:17, William A Rowe Jr wrote: > On Tue, Jan 26, 2016 at 5:16 PM, Jim Jagielski <j...@jagunet.com > <mailto:j...@jagunet.com>> wrote: > > > > On Jan 26, 2016, at 4:39 PM, William A Rowe Jr > <wr...@rowe-clan.net <mailto:wr...@rowe-clan.net>> wrote: > > > > On Tue, Jan 26, 2016 at 3:12 PM, Jim Jagielski <j...@jagunet.com > <mailto:j...@jagunet.com>> wrote: > > I'm assuming that the 'new in 1.6' refers to APR 1.6... > > In which case, I'm not sure what the Warning for > apr_cstr_strtoui64() > > refers to, version-wise. > > > > Good catch, trashing the version reference, but keeping the caution. > > > > > > On Tue, Jan 26, 2016 at 3:15 PM, Jim Jagielski <j...@jagunet.com > <mailto:j...@jagunet.com>> wrote: > > Also, I see apr_cstr_casecmp() but not a case insensitive > version... ?? > > > > casecmp means case-insensitive (c.f. strcasecmp). There is no case- > > sensitive match, at least not yet. Consider strcmp always just > works except > > in a string containing a NULL-octet multibyte continuation > characters, and > > we wouldn't speak any such beast in a C/POSIX locale in the > first place :) > > The description sez: > > "Compare two strings atr1 and atr2, treating case-equivalent > unaccented Latin (ASCII subset) letters as equal." > > which implies, at least to me, case sensitive. I don't read "case > equivalent" as case insensitive... equivalence implies "the same" > to me. > > > Agreed it is very confusing - I had wordsmithed it a bit, but please > feel free > to further correct now that it lives on apr trunk (2.0). In fact, > anyone feel free > to dive in...
Hmph, it's concise, not confusing. Subversion's APIs expect all strings to be encoded in UTF-8, so the docstring can't just say "case-insensitive" because that would be extremely misleading in that context. APR makes no promises about the encoding, but mentioning that these functions are designed to work with the ASCII subset (or EBCDIC equivalent of same) would be quite important, I think? -- Brane
