[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Issue: PATHNAME-SYNTAX-ERROR-TIME (Version 1)
- To: Kent M Pitman <KMP@stony-brook.scrc.symbolics.com>
- Subject: Re: Issue: PATHNAME-SYNTAX-ERROR-TIME (Version 1)
- From: firstname.lastname@example.org (Sandra J Loosemore)
- Date: Fri, 22 Jul 88 11:02:08 MDT
- Cc: email@example.com
- In-reply-to: Kent M Pitman <KMP@STONY-BROOK.SCRC.Symbolics.COM>, Thu, 7 Jul 88 11:23 EDT
Of the options presented for this issue, I prefer
PATHNAME-SYNTAX-ERROR-TIME:PATHNAME-CREATION. The NAMESTRING-COERCION
option seems like it is really the wrong time, and I would rather not
leave it EXPLICITLY-VAGUE.
However, I would really like to see something completely different --
namely adding a keyword argument to TRUENAME to allow it to be used
for explicit syntax checking of filenames without signalling an error
if the file doesn't exist. Functions such as OPEN and the ones in
sections 23.3, 23.4, and 23.5 that actually pass pathnames to the host
file system would be required to (implictly or explicitly) perform the
This would also solve a problem I brought up some time ago, that I was
having with Lucid Lisp under VMS. I had defined a logical name like
LISP$LIBRARY that expanded into something that included a directory
specifier in its expansion, like disk$login:[loosemore.lisp.library].
However, I was getting things like
which the file system naturally barfed on when I tried to open the
file. The problem was that Lucid's PATHNAME function was treating the
logical name like a device specification instead of expanding it.
TRUENAME would have expanded the logical name for me, but since
LISP$LIBRARY was not a complete pathname for an existing file, it
would also have signalled an error.