Branko Äibej wrote:
>William A. Rowe, Jr. wrote:
>
>
>>Let's drop the 'env' concept - this is really useful overall.
>>
>>And please be careful to strip quotes from around elements, and add
>>quotes (or on unix, backslash escape) the seperator element (e.g. colon
>>or semicolon.)
>>
>>
>>
>S
At 03:22 PM 2/5/2003, Branko Čibej wrote:
>This is where it stops working. On Windows, at least on NT-class
>systems, you really do want to use the wide char functions to read the
>environment and convert the result to UTF-8, otherwise we're not safe in
>the presence of characters that can't be rep
William A. Rowe, Jr. wrote:
>++1 if we can go with
>
>APR_DECLARE(apr_status_t) apr_filepath_list_split(
>apr_array_header_t **pathelts, const char *liststr, apr_pool_t *p);
>
>APR_DECLARE(apr_status_t) apr_filepath_list_merge(
>char **liststr, apr_array_header_t *pathelts, apr_pool_t *p);
++1 if we can go with
APR_DECLARE(apr_status_t) apr_filepath_list_split(
apr_array_header_t **pathelts, const char *liststr, apr_pool_t *p);
APR_DECLARE(apr_status_t) apr_filepath_list_merge(
char **liststr, apr_array_header_t *pathelts, apr_pool_t *p);
Let's drop the 'env' concept - thi
I'd like to propose a new function in the apr_filepath module, to be
added for 0.9.2 and/or httpd-2.0.45:
/**
* Split a search path defined in an environment variable (e.g., @c $PATH)
* into separate components
* @ingroup apr_filepath
* @param pathelts the returned components of the search pat
