From ... Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!newsfeeds.belnet.be!news.belnet.be!ossa.telenet-ops.be!nmaster.kpnqwest.net!nreader2.kpnqwest.net.POSTED!not-for-mail Newsgroups: comp.lang.lisp Subject: Re: "nonstandard" characters in logical pathnames References: <3CB70B46.6B82AE24@eurocom.od.ua> Mail-Copies-To: never From: Erik Naggum Message-ID: <3227620587344875@naggum.net> Organization: Naggum Software, Oslo, Norway Lines: 25 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 12 Apr 2002 17:16:27 GMT X-Complaints-To: newsmaster@KPNQwest.no X-Trace: nreader2.kpnqwest.net 1018631787 193.71.199.50 (Fri, 12 Apr 2002 19:16:27 MET DST) NNTP-Posting-Date: Fri, 12 Apr 2002 19:16:27 MET DST Xref: archiver1.google.com comp.lang.lisp:31535 * Vladimir Zolotykh | Is it possible to deal that way with files which names contains _ | (underscore)? Logical pathnames are intended as system-independent pathnames that you map to real pathnames in a particular system. It is a unidirectional mapping. Note that there is no way to get from a physical pathname to a logical pathname in the language. Using this strong hint, you should realize that there is no intention in the language to be able to create a logical pathname for all physical pathname. Basically, you enumerate the files you want to exist for your application using logical pathnames, and then you arrange for this to be true in any given physical file system. If you want to refer to existing filenames on the system over which your application has no (naming) control, use physical pathnames. That is what they are for. /// -- In a fight against something, the fight has value, victory has none. In a fight for something, the fight is a loss, victory merely relief. Post with compassion: http://home.chello.no/~xyzzy/kitten.jpg