On 26.11.2015 15:44, William A Rowe Jr wrote:
> Better if I address this Q to svn folks at the APR project :)
> 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.

Note that the svn_cstring* functions have *nothing* whatsoever to do
with the "C" locale; they manipulate nul-terminated "C" strings, that's all.

svn_cstring_casecmp depends on svn_ctype_casecmp; the svn_ctype
functions are expected to only work on the ASCII subset.

-- Brane


>> 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)
>>>> Bert
>>>>
>>>> From: William A Rowe Jr [mailto:wr...@rowe-clan.net]
>>>> Sent: woensdag 25 november 2015 22:55
>>>> To: httpd <d...@httpd.apache.org>
>>>> Subject: Re: apr_token_* conclusions (was: Better casecmpstr[n]?)
>>>>
>>>> On Wed, Nov 25, 2015 at 3:52 PM, Christophe JAILLET <
>>> christophe.jail...@wanadoo.fr> wrote:
>>>>> Hi,
>>>>>
>>>>> just in case off, gnome as a set of function g_ascii_...
>>>>> (see
>>> https://developer.gnome.org/glib/2.28/glib-String-Utility-Functions.html#g-ascii-strcasecmp
>>> )
>>>> Interesting, does anyone know offhand whether these perform the expected
>>>> or the stated behavior under EBCDIC environments?
>>>

Reply via email to