|
From: Nikodemus S. <nik...@ra...> - 2013-02-04 16:43:46
|
On 4 February 2013 18:07, CRLF0710 <crl...@gm...> wrote: > > 2013/2/4 Christophe Rhodes <cs...@ca...> >> >> with a bracket in it, you can escape the wildness using backslashes: >> (wild-pathname-p #p"\\[") ; => nil > > > However, this is not possible under Windows platform, since the > character #\\ is used as the separator for directories for Windows path > name. > For example, we say #P"C:\\test.txt". See: MAKE-PATHNAME, SB-EXT:PARSE-NATIVE-NAMESTRING, and SB-EXT:NATIVE-PATHNAME. Not that I dispute the fact that having escape character and supported pathname separator leads to epic levels of lossage. (I would actually be inclined to accept as a directory separator \ only in native Windows namestrings, but I suppose that getting (pathname "C:\\foo\\bar") wrong would be at least moderately painful for Windows users... so another solution seems called for.) Cheers, -- Nikodemus |