Issue: PATHNAME-PRINT-READ (Version 1)

[Eric Benson <eb@lucid.com>]

For Current Practice:

Lucid CL also implements the proposed behavior.

For Cost to Users:

Users who define their own #P read macro may be unhappy.


I weakly support this change.  I wish someone would make a proposal
for generic pathnames.  I don't think they ever got the consideration
they deserved.  (I know they aren't really related to this issue,
except insofar as users would like to have portable pathnames in their
programs.)