On Tue, Oct 05, 2004 at 09:09:31AM -0500, Brian Ford wrote: >On Tue, 5 Oct 2004, Corinna Vinschen wrote: > >> Chris, I might be missing something but that looks like a bug in >> conv_path_list to me. Why is conv_fn called with "." for empty >> strings instead of ignoring the empty path? >> >> Is an empty path component a windowzism I don't know about? > >I don't know if it's part of any standard, but it's a *NIXism. From >Solaris 8 "man sh": > >Execution: > >The current directory is specified by a null path name, which can appear >immediately after the equal sign, between two colon delimiters anywhere in >the path list, or at the end of the path list. > >"man ksh" > >Execution: > >The default path is /bin:/usr/bin: (specifying /bin, /usr/bin, and the >current directory in that order). > >The current directory can be specified by two or more adjacent colons, or >by a colon at the beginning or end of the path list. > >etc... > >I believe this is a valid construct and I have used it frequently.
Ditto. PATH=/foo::/bar means search for /foo, then the current directory, then /bar. cgf