Hi,
I just noticed that the PATHNAME-TYPE of COMPILE-FILE-PATHNAME differs
depending on whether I use a pathname with a logical host or not:
| CMU Common Lisp 18d, running on interim.henrik-motakef.de
| Send questions to [EMAIL PROTECTED] and bug reports to [EMAIL PROTECTED]
| Loaded subsystems:
| Python 1.0, target Intel x86
| CLOS based on PCL version: September 16 92 PCL (f)
| * (setf (logical-pathname-translations "foo")
| '(("**;*.*.*" "/home/henrik/foo/**/")))
| (("**;*.*.*" "/home/henrik/foo/**/"))
| * (pathname-type (compile-file-pathname "foo.lisp"))
| "x86f"
| * (pathname-type (compile-file-pathname "foo:foo.lisp"))
| "FASL"
| * (pathname-type (compile-file-pathname
| (translate-logical-pathname "foo:foo.lisp")))
| "x86f"
| * (compile-file #p"foo:foo.lisp")
| Byte Compiling Top-Level Form:
|
| #p"/pokey/usr/home/henrik/foo/foo.fasl"
| NIL
| NIL
| * (compile-file "/home/henrik/foo/foo.lisp")
| Byte Compiling Top-Level Form:
|
| #p"/pokey/usr/home/henrik/foo/foo.x86f"
| NIL
| NIL
Is this supposed to work that way? If so, why?
Background: I tried to set up a logic host in a way that fasls for
different lisps are stored in different subdirectories, i.e. it would
really look something like this:
| (setf (logical-pathname-translations "foo")
| '(#+cmu ("**;*.x86f" "/home/henrik/foo/cmucl-fasl/**/")
| #+clisp ("**;*.fas" "/home/henrik/foo/clisp-fasl/**/")
| ("**;*.*.*" "/home/henrik/foo/**/")))
AFAICS, I need to know the pathname-type of fasls for this to
work. How do I get it before having set up the pathname translations?
tia
Henrik
