From ...
From: Erik Naggum <erik@naggum.no>
Subject: Re: A portable DIRECTORY-P. Re: Here we go again. More CMUCL/ACL pathname differences.
Date: 1999/01/13
Message-ID: <3125218436594568@naggum.no>#1/1
X-Deja-AN: 432101686
References: <778kqn$2b2$1@nnrp1.dejanews.com> <efyyanagarp.fsf@whizzy.cc.gatech.edu> <77bdqi$9fk$1@nnrp1.dejanews.com> <3125045622004774@naggum.no> <77e4e3$jrj$1@nnrp1.dejanews.com> <87d84lpaxr.fsf_-_@2xtreme.net> <3125142331394422@naggum.no> <77hsu3$ckt$1@nnrp1.dejanews.com>
mail-copies-to: never
Organization: Naggum Software; +47 8800 8879; http://www.naggum.no
Newsgroups: comp.lang.lisp

* vnikolov@poboxes.com
| Isn't (something like) LOGICAL-PATHNAME-NAMESTRING-P really
| what is needed?  That's not so trivial.

  sigh.

(defun logical-pathname-namestring-p (namestring)
  (typep (ignore-errors (parse-namestring namestring)) 'logical-pathname))

| On a related issue:
| Wasn't it Erik Naggum who wrote that ACL has #L precisely
| because sometimes one wants to force a namestring to be
| parsed as a logical pathname.

  care to share the intermediate assumptions and/or your conclusions that
  might tie this unrelated "issue" to something?  I actually think you're
  missing something really fundamental to parsing namestrings, and it would
  be a boon for everyone if you would realize it and try to understand,
  especially for me if you are going to continue to post "related issues"
  that aren't but which inexplicably refer to something I have said which
  you obviously didn't understand, either.

#:Erik