;; There is a great degree of variability permitted here.  The next
 ;; several examples are intended to illustrate just a few of the many
 ;; possibilities.  Whether the name is canonicalized to a particular
 ;; case (either upper or lower) depends on both the file system and the
 ;; implementation since two different implementations using the same
 ;; file system might differ on many issues.  How information is stored
 ;; internally (and possibly presented in #S notation) might vary,
 ;; possibly requiring `accessors' such as PATHNAME-NAME to perform case
 ;; conversion upon access.  The format of a namestring is dependent both
 ;; on the file system and the implementation since, for example, one
 ;; implementation might include the host name in a namestring, and
 ;; another might not.  #S notation would generally only be used in a
 ;; situation where no appropriate namestring could be constructed for use
 ;; with #P.
 (setq p1 (pathname "test"))
⇒  #P"CHOCOLATE:TEST" ; with case canonicalization (e.g., VMS)
OR⇒ #P"VANILLA:test"   ; without case canonicalization (e.g., Unix)
OR⇒ #P"test"
OR⇒ #S(PATHNAME :HOST "STRAWBERRY" :NAME "TEST")
OR⇒ #S(PATHNAME :HOST "BELGIAN-CHOCOLATE" :NAME "test")
 (setq p2 (pathname "test"))
⇒  #P"CHOCOLATE:TEST"
OR⇒ #P"VANILLA:test"
OR⇒ #P"test"
OR⇒ #S(PATHNAME :HOST "STRAWBERRY" :NAME "TEST")
OR⇒ #S(PATHNAME :HOST "BELGIAN-CHOCOLATE" :NAME "test")
 (pathnamep p1) ⇒  true
 (eq p1 (pathname p1)) ⇒  true
 (eq p1 p2)
⇒  true
OR⇒ false
 (with-open-file (stream "test" :direction :output)
   (pathname stream))
⇒  #P"ORANGE-CHOCOLATE:>Gus>test.lisp.newest"