[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Issue: PATHNAME-SUBDIRECTORY-LIST, PATHNAME-COMPONENT-CASE, PATHNAME-WILD
- To: firstname.lastname@example.org
- Subject: Issue: PATHNAME-SUBDIRECTORY-LIST, PATHNAME-COMPONENT-CASE, PATHNAME-WILD
- From: masinter.pa@Xerox.COM
- Date: 19 Sep 88 16:23 PDT
I think it might be worthwhile to organize the pathname issues by operating
system, e.g., What's the right way for CL to talk to Unix-like file systems? To
Mac-like file systems? To VMS-like file systems?
At least for PATHNAME-COMPONENT-CASE, PATHNAME-CANONICAL-LIST, PATHNAME-WILD,
There seem to be more PATHNAME issues than file-naming conventions. Further, it
seems more important to reach convergence within an operating system than across
them; for example, there's no good reason why the 7 different CLs available for
various UNIX systems should treat file names differently, or those within the
Mac world should treat those names differently. If we can get convergence among
implementors of CL within OS classes, we might well be able to sort out which
things are really different because the host OS is different?
What do you think?