Re: [clisp-list] Pathnames...

[Christophe R. <cs...@ca...>]

On Wed, May 30, 2001 at 01:48:19PM -0400, Sam Steingold wrote:
> > * Honorable Christophe Rhodes <cs...@ca...> writes:
> >
> > However, clisp -ansi as of this morning gives:
> 
> if you live on the bleeding edge, you should subscribe to clisp-devel.

In that case, please change your moderation message, which quite
clearly told me to send this mail to clisp-list, or else allow
messages through from non-subscribers. I have no particular desire to
receive CVS commit mails, though I do follow them on geocrawler.
 
> > [23]> (compile-file-pathname #p"cl-library:;metering;metering.lisp")
> > 
> > *** - PARSE-NAMESTRING: argument should be a string, symbol, file
> >       stream or pathname, not #<UNBOUND>
> 
> I do not observe this.  

In clisp -ansi?

> Moreover, #p"cl-library:;metering;metering.lisp"
> is not a logical pathname.

It is if -ansi is enabled (I believe correctly):

clisp -ansi
[1]> (setf (logical-pathname-translations "CL-LIBRARY") 
           (list '(";**;*.*.*" "/tmp/clisp/**/*.*")))
((#S(LOGICAL-PATHNAME :HOST "CL-LIBRARY" :DEVICE NIL
     :DIRECTORY (:RELATIVE :WILD-INFERIORS) :NAME :WILD :TYPE :WILD
     :VERSION :WILD)
  "/tmp/clisp/**/*.*"))
[2]> #p"CL-LIBRARY:;foo;bar.lisp"
#S(LOGICAL-PATHNAME :HOST "CL-LIBRARY" :DEVICE NIL :DIRECTORY (:RELATIVE "FOO")
   :NAME "BAR" :TYPE "LISP" :VERSION NIL)

Are you claiming that this should not be the case?

> (compile-file-pathname (logical-pathname "clocc:clocc.lisp"))
> is buggy, and, hopefully, will be fixed shortly.

Great, thanks.

Cheers,

Christophe
-- 
Jesus College, Cambridge, CB5 8BL                           +44 1223 524 842
http://www-jcsu.jesus.cam.ac.uk/~csr21/                  (defun pling-dollar 
(str schar arg) (first (last +))) (make-dispatch-macro-character #\! t)
(set-dispatch-macro-character #\! #\$ #'pling-dollar)