[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Issue: PATHNAME-SUBDIRECTORY-LIST (Version 4)
- To: Moon@STONY-BROOK.SCRC.Symbolics.COM
- Subject: Issue: PATHNAME-SUBDIRECTORY-LIST (Version 4)
- From: firstname.lastname@example.org (Aaron Larson)
- Date: Thu, 23 Mar 89 00:38:34 CST
- Cc: cl-cleanup@SAIL.STANFORD.EDU
- In-reply-to: David A. Moon's message of Wed, 22 Mar 89 21:59 EST <19890323025928.1.MOON@EUPHRATES.SCRC.Symbolics.COM>
- Posted-date: Thu, 23 Mar 89 00:38:34 CST
Allow the value of a pathname's directory component to be a list. The
car of the list may be either of the symbols :ABSOLUTE or :RELATIVE.
Each remaining element of the list is a string or one of the keyword
symbols listed below...
I picked on Kent for not specifying that the elements of the list should be
either strings or keywords, then after reading PATHNAME-WILD, I think that
we should not preclude implmentations from defining "regular expression",
or "user home directory"components. E.g.
(pathname-directory x) => (:absolute "foo" #<regexp "Fo" :wild "bar">)
(pathname-directory x) => (#<user-homedir "alarson"> "bar" "baz")
I'm not advocating adding such a feature, just not precluding us from
defining one in the future. Perhaps we should add a line something like:
"Implementations may permit objects of types other than keywords and
strings as elements of the pathname-directory list."
Even without a statement of this kind, I support the proposal.