From f5758b15bef369f70a9fde9bbdc8a176151ca54d Mon Sep 17 00:00:00 2001 From: rtoy <rtoy> Date: Thu, 10 Feb 2005 15:57:08 +0000 Subject: [PATCH] As noted by Dan Corkill, cmucl-imp, 2005-02-08, :unspecific should be accepted when computing namestrings. CLHS 19.2.2.2.3.1 says :unspecific components should not appear in the namestring. Make it so. --- code/filesys.lisp | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/code/filesys.lisp b/code/filesys.lisp index fce3aa60f..a341c6c8c 100644 --- a/code/filesys.lisp +++ b/code/filesys.lisp @@ -6,7 +6,7 @@ ;;; Scott Fahlman or slisp-group@cs.cmu.edu. ;;; (ext:file-comment - "$Header: /Volumes/share2/src/cmucl/cvs2git/cvsroot/src/code/filesys.lisp,v 1.85 2004/12/13 15:12:54 rtoy Exp $") + "$Header: /Volumes/share2/src/cmucl/cvs2git/cvsroot/src/code/filesys.lisp,v 1.86 2005/02/10 15:57:08 rtoy Exp $") ;;; ;;; ********************************************************************** ;;; @@ -357,6 +357,10 @@ (defun unparse-unix-piece (thing) (etypecase thing ((member :wild) "*") + ((member :unspecific) + ;; CLHS 19.2.2.2.3.1 says "That is, both nil and :unspecific + ;; cause the component not to appear in the namestring." + "") (simple-string (let* ((srclen (length thing)) (dstlen srclen)) -- GitLab