Thanks a lot for the fix! I looked at it, it works, but it's slightly subtle and...
OK so using that clisp, all tests pass (slowly). But since it's a heisenbug, it could...
Also, I seem to be lacking access rights and can't change the bug title.
I tried adding --with-debug CC='g++' and it failed to compile: > form: (nth-prime...
Wow, in my scripts #p"ASDF:test;" is parsed correctly, but not at the SLIME command-line....
Regarding #2, here are (COMPILE-FILE '#P"ASDF:TEST;LOGICAL-FILE.LISP.NEWEST" ':OUTPUT-FILE...
Regarding 2, the merging seems to go wrong: The directory seems to be wholly taken...
Final note: it is probably a bad thing to call logical pathnames "portable pathnames"....
For the record, this is the call that returns fishy results: (COMPILE-FILE-PATHNAME...
I tried adding --with-debug CC='g++' and it failed to compile: form: (nth-prime 100)...
The definition of the host doesn't seem to matter. See example. Duh. Attached. Maybe...
Regarding 2, the merging seems to go wrong: The directory seems to be wholly taken...
This bug may be renamed from "Instability in pathname handling" to "Deterministic...
I believe this is a different bug, and possibly not directly related to pathname...
Regarding 1- I found out why my script could parse logical pathnames but not my SLIME...
Regarding #2, here are (COMPILE-FILE '#P"ASDF:TEST;LOGICAL-FILE.LISP.NEWEST" ':OUTPUT-FILE...
Wow, in my scripts #p"ASDF:test;" is parsed correctly, but not at the SLIME command-line....
Regarding point 1-, I of course meant translate-logical-pathname, not translate-pathname...
I carefully wrote a response, and sourceforge looks like it ate it. Sigh. 1- logical...
Instability in pathname handling
logical pathnames and letter case gone wrong
posix:file-stat fails on directory on Windows