;;; FIXME: currently SBCL throws NAMESTRING-PARSE-ERROR: should this be
;;; a TYPE-ERROR?
-;; error: directory-component not valid
(assert (not (ignore-errors
(make-pathname :host "FOO" :directory "!bla" :name "bar"))))
(assert (equal (namestring (translate-logical-pathname
"test0:foo;bar;baz;mum.quux.3"))
"/library/foo/foo/bar/baz/mum.quux"))
-
+\f
;;;; MERGE-PATHNAME tests
;;;;
;;;; There are some things we don't bother testing, just because they're
;;;; other implementations, they depend quite heavily on the rules for
;;;; namestring parsing, which are implementation-specific. So, success
;;;; or failure in these tests doesn't tell you anything about
-;;;; ansi-compliance unless your PARSE-NAMESTRING works like ours.
+;;;; ANSI-compliance unless your PARSE-NAMESTRING works like ours.
(setf (logical-pathname-translations "scratch")
'(("**;*.*.*" "/usr/local/doc/**/*")))
;; === logical pathnames ===
;; recognizes a logical pathname namestring when
;; default-pathname is a logical pathname
- ;; FIXME: 0.6.12.20 fails this one.
+ ;; FIXME: 0.6.12.23 fails this one.
#+nil (#P"scratch:foo;name1" #p"name1" #p"scratch:foo;")
;; or when the namestring begins with the name of a defined
;; logical host followed by a colon [I assume that refers to pathname
(#p"SCRATCH:ABSOLUTE;PATH;NAME.TYPE"
#p"scratch:absolute;path;name" #p"/dir/default-name.type")
- ;; TODO: test version handling in LPNs
+ ;; FIXME: test version handling in LPNs
)
do (assert (string= (namestring (apply #'merge-pathnames params))
(namestring expected-result))))