[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Issue: PATHNAME-EXTENSIONS (Version 1)
- To: Kent M Pitman <KMP@STONY-BROOK.SCRC.Symbolics.COM>
- Subject: Re: Issue: PATHNAME-EXTENSIONS (Version 1)
- From: David N Gray <Gray@DSG.csc.ti.com>
- Date: Tue, 3 Jan 89 12:16:46 CST
- Cc: CL-Cleanup@SAIL.STANFORD.EDU
- In-reply-to: Msg of Wed, 28 Dec 88 15:57 EST from Kent M Pitman <KMP@STONY-BROOK.SCRC.Symbolics.COM>
- Sender: GRAY@Kelvin.csc.ti.com
> Clarify that COMMON-PATHNAME-P considers a pathname's host field
> to fit the Common Lisp pathname model if the filler of the host
> field is a string (naming a host), and not otherwise.
... etc.
Rather than talk about the "fields" of a pathname, I think it would be
better to talk about the value returned by the standard accessor
functions. For example, in proposal PATHNAME-SUBDIRECTORY-LIST, you
suggested that an implementation could use a non-standard representation
internally so long as the function PATHNAME-DIRECTORY returned the
standard representation. Thus, we could say:
Clarify that COMMON-PATHNAME-P returns true if PATHNAME-HOST will
return a string, and NIL if PATHNAME-HOST will return something else.
etc.