[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Issue: PATHNAME-SUBDIRECTORY-LIST (Version 4)
- To: pierson@mist.encore.com
- Subject: Issue: PATHNAME-SUBDIRECTORY-LIST (Version 4)
- From: Jim McDonald <jlm@lucid.com>
- Date: Thu, 23 Mar 89 11:04:50 PST
- Cc: cl-cleanup@sail.stanford.edu
- In-reply-to: Dan L. Pierson's message of Thu, 23 Mar 89 11:07:02 EST <8903231607.AA04217@mist.>
I'm also disturbed by the proposed restrictions on the elements of a
pathname-directory list. Why, for example, is it necessary to
preclude a feature that allows variables to appear? E.g., the
following seems like a plausibly useful pair of pathnames:
(:ABSOLUTE *top-of-source-tree* "a" "b" "c")
(:ABSOLUTE *top-of-destination-tree* "a" "b" "c")
or even:
(:ABSOLUTE *top-of-source-tree* . *relative-dir-path*)
(:ABSOLUTE *top-of-destination-tree* . *relative-dir-path*)
[There's probably better syntax than a dotted pair, but you know what
I mean.]
I'm not saying I need or even want this particular feature, but I'm
pretty sure I don't want to have it prohibited just because it hadn't
occurred to anyone yet.
[Btw, I think Alarson's example for home dir could be accomomdated as
(... :HOME "alarson" ...) in the spirit of the proposal. Most
plausible structures could probably be handled similarly, but perhaps
clumsily.]
jlm