From ... Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!newsfeeds.belnet.be!news.belnet.be!news2.kpn.net!news.kpn.net!nslave.kpnqwest.net!nloc.kpnqwest.net!nmaster.kpnqwest.net!nreader1.kpnqwest.net.POSTED!not-for-mail Newsgroups: comp.lang.lisp Subject: Re: logical pathnames - lack of info? References: <877kp6hdjh.fsf@blitz.comp.com> <3C756CF1.B1AA8D77@nyc.rr.com> Mail-Copies-To: never From: Erik Naggum Message-ID: <3223361449720827@naggum.net> Organization: Naggum Software, Oslo, Norway Lines: 20 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 22 Feb 2002 10:10:45 GMT X-Complaints-To: newsmaster@KPNQwest.no X-Trace: nreader1.kpnqwest.net 1014372645 193.71.199.50 (Fri, 22 Feb 2002 11:10:45 MET) NNTP-Posting-Date: Fri, 22 Feb 2002 11:10:45 MET Xref: archiver1.google.com comp.lang.lisp:27096 * Kenny Tilton | if they are amazingly obvious they should be easy to explain Quite the contrary. The obvious eludes explanation. It usually takes a trained philosopher to see things are obvious to most people from an unobvious angle and describe it back to them in terms that interest them much more than the obvious matter at hand would. | the doc is so bad we cannot even formulate questions, that is why we | simply ask where to find good doc. I find this a rather peculiar position, but since I read this from the specifications and tend to use pathname translations to provide a virtual file system that is far easier to maneuver than the physical file system I have to work on, I really do wonder what the problem is. /// -- 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.