Grudgingly accept that folks may want to merge paths containing wildcard

  characters... fail similarly to ENOENT/ENOTDIR, where we return the path
  but emit the error as a precaution.  Folks interested in the results of
  an invalid path merge need to look for those APR_STATUS_IS_xxx() results.


git-svn-id: http://svn.apache.org/repos/asf/apr/apr/trunk@64213 13f79535-47bb-0310-9956-ffa450edef68

1 files changed, 5 insertions, 0 deletions

diff --git a/include/apr_file_info.h b/include/apr_file_info.h
index 2a6d0802e..717858d9e 100644
--- a/include/apr_file_info.h
+++ b/include/apr_file_info.h
@@ -373,6 +373,11 @@ APR_DECLARE(apr_status_t) apr_filepath_root(const char **rootpath,
  * @param flags the desired APR_FILEPATH_ rules to apply when merging
  * @param p the pool to allocate the new path string from
  * @deffunc apr_status_t apr_filepath_merge(char **newpath, const char *rootpath, const char *addpath, apr_int32_t flags, apr_pool_t *p)
+ * @remark if the flag APR_FILEPATH_TRUENAME is given, and the addpath 
+ * contains wildcard characters ('*', '?') on platforms that don't support 
+ * such characters within filenames, the paths will be merged, but the 
+ * result code will be APR_EPATHWILD, and all further segments will not
+ * reflect the true filenames including the wildcard and following segments.
  */                        
 APR_DECLARE(apr_status_t) apr_filepath_merge(char **newpath, 
                                              const char *rootpath,