From ... Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!logbridge.uoregon.edu!newsfeed.esat.net!nslave.kpnqwest.net!nloc.kpnqwest.net!nmaster.kpnqwest.net!nreader3.kpnqwest.net.POSTED!not-for-mail Newsgroups: comp.lang.lisp Subject: Re: Packages in CMUCL References: <87sn6ch11f.fsf@darkstar.cartan> Mail-Copies-To: never From: Erik Naggum Message-ID: <3226952770770630@naggum.net> Organization: Naggum Software, Oslo, Norway Lines: 21 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 04 Apr 2002 23:45:54 GMT X-Complaints-To: newsmaster@KPNQwest.no X-Trace: nreader3.kpnqwest.net 1017963954 193.71.199.50 (Fri, 05 Apr 2002 01:45:54 MET DST) NNTP-Posting-Date: Fri, 05 Apr 2002 01:45:54 MET DST Xref: archiver1.google.com comp.lang.lisp:31079 * Nils Goesche | Hm. Isn't the idea of lots of REQUIRE's and PROVIDE's hidden all over | the place much more repulsive? From the HyperSpec: | | # If the pathname-list is nil, an implementation-dependent mechanism | # will be invoked in an attempt to load the module named module-name; | | so it doesn't look very portable, either. But this is what makes it portable. How you organize files on a system is not portable, so if you do what require needs on every system, what the single (require :foobar) does is portably ensure that feature :foobar is portably loaded in every system, regardless of how that actually works on each system. /// -- 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