From: Sam S. <sd...@gn...> - 2008-12-22 19:10:10
|
Raymond Toy wrote: > What do you mean "ftp to it"? ftp(1) > Does (open "prep:clisp" ...) recognize > prep as an internet host and open an ftp connection to it? it could - given a good standard. > I'm also confused on how an ftp location is related to whether > "prep:clisp" is a logical pathname or not. the notion of logical pathnames was introduced to enable automatic pathname transformations. they were kept "separate" from the physical pathnames with a uniquely recognizable syntax to avoid confusion. the problem is that some perfectly physical pathnames like "prep:emacs" looks like logical pathnames. a better approach, IMO, would have been to have pathnames with just 3 fields: host, directory and name, and have all pathname operations (OPEN, TRUENAME &c) dispatch on host. alas, it is too late now. >> yes, but the standard does not allow you to save the pathnames to >> files in a readable format. > Won't #.(make-pathname <args>) work? (Well, it won't if you *read-eval* > is NIL.) make-pathname does some non-trivial processing. also, it is NOT used by (with-standard-io-syntax (write pathname)). Sam. |