uiop parse-native-namestring portability?

Raymond Toy toy.raymond at gmail.com
Thu Jan 7 16:43:55 UTC 2016

>>>>> "Jared" == Jared C Davis <jared.c.davis at gmail.com> writes:

    Jared> Hi,
    Jared> Should I be able to expect the following to behave consistently across Lisps?

    Jared> (file-namestring (uiop:parse-native-namestring "."))

    Jared> I find that:

    Jared> - CCL and SBCL produce "."
    Jared> - Allegro produces NIL
    Jared> - CMUCL signals an error in LISP::UNPARSE-UNIX-FILE

    Jared> If I just look at:

    Jared> (uiop:parse-native-namestring ".")

    Jared> I get:

    Jared> Allegro:  #P"./"
    Jared> CCL:      #P"."
    Jared> SBCL:     #P"."
    Jared> CMUCL:    #P(:NAME "." :TYPE :UNSPECIFIC)

I wonder why uiop:parse-native-namestring does that on cmucl.
(cl:parse-namestring ".") returns #p"./", which, I think, makes sense.

Without examining the actual slots, it's hard to tell what #p"."
really is.


More information about the asdf-devel mailing list