Re: split-path weirdness on Windows with UNC paths

[Hannu Koivisto <azure@iki.fi>]

Matthew Flatt <mflatt@cs.utah.edu> writes:

| Quoting Hannu Koivisto:
...
| > #f
| > "//lancaster/prj/"
| > #t
| > 
| 
| I claim that this is correct, on the grounds that "//lancaster/prj/" is
| a volume name (just like "c:/"). 

Ah, of course, you are right, I didn't think of the whole thing as
a volume name; it's been almost two years since I've actively used
Windows.  I was further confused by the fact that for my use, a
minimalistic emulation of CL's pathname system, I thought to
separate lancaster, in that particular example, as host part, not
device (with prj).  Hm.  Oh well, it doesn't really matter in
practise whether it's a host or device in my use.

Thanks for the insight,
-- 
Hannu