Raymond Toy <[EMAIL PROTECTED]> writes: > CL-USER> (MAKE-PATHNAME :DEFAULTS "v:systems;" > :VERSION :NEWEST > :NAME "v" > :TYPE "asd" > :CASE :LOCAL) > #.(logical-pathname "V:SYSTEMS;v.asd")
OK, I think this is strictly a grey area of the spec (surprise ...). The characters in logical pathname _namestrings_ must be uppercase, digits or #\-, and lowercase characters are uppercased (see CLHS 19.3.1.1.7). I don't see a lot in CLHS about what happens if you put other kinds of character in an LPN component directly - i.e. without using the pathname parser. I would argue that good taste suggests they should also be uppercased, but I can't find anything that I would regard as mandating it. Note that if your printed representation of such an LPN involves a namestring (as above), you don't have print-read consistency, because reading that printed representation will do the uppercasing ... > Perhaps the right thing is to convert any lower case parts to upper > case when the pathname is a logical pathname. I think this is right even if it's not required by the letter of the standard. But then I would, as it's what SBCL does ;-) -dan -- "please make sure that the person is your friend before you confirm" -- Attached file included as plaintext by Listar -- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQBApBFyHDK5ZnWQiRMRAitxAJ4uMAhZ5A1YBW0tqoOJX+V/hXSLvQCeO5xc XriMnGqBKkpKycZmvy/EmJM= =qrjG -----END PGP SIGNATURE-----
