From ... From: Erik Naggum Subject: Re: Logical pathname hosts. Date: 1998/12/21 Message-ID: <3123226970741221@naggum.no>#1/1 X-Deja-AN: 424455138 References: <75k4tr$uom$1@nnrp1.dejanews.com> <3123192188393170@naggum.no> <75l1qu$lum$1@nnrp1.dejanews.com> mail-copies-to: never Organization: Naggum Software; +47 8800 8879; http://www.naggum.no Newsgroups: comp.lang.lisp * robert_m_miles@yahoo.com | Thank you. This worked on the Redhat ACL5 I downloaded, but does not | work on the CMUCL I downloaded. CMUCL's support for logical pathnames is known to be lacking. | I've been reading the hyperspec about the pathname stuff, but I'm pretty | confused. It seems like it's possible to specify a trunk like I did | above with ext:search-list except using ANSI CL and then do an equivalent | load statement something like: (load "lisp:source;demos;foo.lisp") ; | maybe not with the ".lisp" (????) Is this possible? yes, logical pathname hosts have directory structure. this should be fairly evident from the specification, but it seems that you insist on trying to fit the specification into your existing mindset instead of trying to understand the specification. this simply won't work. you have to understand first, then apply your understanding back at what you were used to. | It probably should work with CMUCL but maybe I screwed up somewhere. I suggest you avoid CMUCL if you want to learn about logical pathnames. incidentally, I disagree with some of what Allegro CL 5.0 does, as well, and have applied some advice to get what I think is the right way to do it, since I use logical pathnames extensively. #:Erik -- Nie wieder KrF! Nie wieder KrF! Nie wieder KrF! Nie wieder KrF!