Hello! Andy Wingo <wi...@pobox.com> writes:
> On Mon 02 May 2011 22:58, l...@gnu.org (Ludovic Courtès) writes: [...] > The funny thing is that this doesn't matter at all. Well, I mean that > it's valid to construct pathnames with / as the separator on Windows, as > / and \ are equivalent there. Oh, good. > I still think that we need at least the ability to pass a bytevector as > a path name, on GNU systems; and that if we can do so, then any routine > that needs to deal with a path name would then need to deal in byte > vectors in addition to strings, and at that point perhaps it is indeed > useful to have a path library. To accommodate various file name encodings, right? Then yes. I think GLib and the like expect UTF-8 as the file name encoding and complain otherwise, so UTF-8 might be a better default than locale encoding (and it’s certainly wiser to be locale-independent.) >> Vicinities in SLIB/SCM are similar, with ‘vicinity:suffix?’ >> abstracting over slash vs. backslash [2]. I’m not sure how they handle >> MS-DOS volume names. > > I don't think that they do handle volume names; at least, from what I > could see in the API description there. So volumes matter in the file name canonicalization of the .go cache right? Couldn’t we mimic /cygdrive/c, etc.? Thanks, Ludo’.
