Re: Simplicity of timespec section, and exec-path-list rationale Lassi Kortela 31 Jul 2019 15:15 UTC

>     On Windows, semicolon is the PATH separator. Even if we don't provide a
>     `getenv` procedure in this SRFI, perhaps we should provide a string
>     constant that gives the path separator. `path-list-separator`?
>
> Good idea, although path-separator is probably clear enough.

 From experience: it's not clear enough. It is easily confused with the
pathname component separator (slash on Unix or backslash on Windows).
One could say the latter is the "directory separator", but PATH is a
list of directories so it's no clearer :)

More generally, the name PATH (as a singular word) is itself confusing.
People usually think of "path" as an abbreviation of "pathname", so a
more intuitive name for PATH would be PATHS. We can't fix that oversight
but we can be extra clear in any new names we invent.