Subject: Re: ACL, CLISP and pathnames
From: Erik Naggum <>
Date: 1998/05/12
Newsgroups: comp.lang.lisp
Message-ID: <>

* Sam Steingold
| So, ACL cannot read what CLISP writes readably.

  like that's a bombshell.

| Whose bug is this - ACL's or CLISP's?

  why is that even a question?  CLISP has a _really_ bad rap sheet when it
  comes to conformance, and there's _nothing_ to support its behavior in
  this case, either.  neither the #S(PATHNAME ...) hack nor the stupid
  #"..." form is anywhere _near_ standard.  (this is not to imply that
  Allegro CL is always a priori conforming, but when you have a case of
  total lack of support for the opponent, why look further?)

| CLHS doesn't seem to specify #S syntax for pathnames, only #p, so,
| apparently, ACL is standard-compliant here.  Or am I missing something?

  no, Allegro CL is conforming.

| Is there a simple workaround?

  yes, write your own print method for pathnames in CLISP.

| Can I advise ACL to call `make-pathname' when seeing #S(PATHNAME)?

  not that I know of.

  Support organized crime: use Microsoft products!