> > On Nov 26, 2015 08:39, "William A Rowe Jr" <wr...@rowe-clan.net> wrote: > >> Sounds right... Actually a fusion between svn_cstring_* and several >> existing ap_ and apr_ functions would be useful. >> >> SVN folk, any objection to APR appropriating these API's? 20/20 >> hindsight, is apr_cstring_ or shorter apr_cstr_ the way to go here? You >> all had to use the thing so I trust your preferences. Either expresses >> locale C in my mind, so they work for me. >> On Nov 26, 2015 07:38, "Jim Jagielski" <j...@jagunet.com> wrote: >> >>> Yeah, SVN's 'svn_cstring_casecmp' and how it's used is >>> pretty much inline with my thoughts on how httpd would >>> use ours... >>> >>> > On Nov 25, 2015, at 5:10 PM, Bert Huijben <b...@qqmail.nl> wrote: >>> > >>> > We have a set of similar comparison functions in Subversion. I’m >>> pretty sure we already had these in the time we still had ebcdic support on >>> trunk. >>> > (We removed that support years ago, but the code should still live on >>> a branch) >>> >> Given our long preference for short-ish names (apr_sockaddr, apr_finfo_ etc...), the fact that apr_cstr_ can be read as 'C String' functions (which could reflect the programming language and also its C/Posix locale), I have time this week to add the svn work and start tracking down candidates/equivilance between that apr_cstr_ API and httpd's functions/use case. Yann replied that apr_cstr_ is acceptable to him, didn't hear any other feedback except Greg's clarification of what svn_cstring_ means.
If there are any last minute reservations about that naming convention, please holler.
