--- "Pierre R. Mai" <[EMAIL PROTECTED]> wrote: [snip] > REQUIRE seriously only ever works halfway decently to load > implementation-supplied stuff (if that is the documented way to do > it), and even this usage is obviously implementation-dependent. > > > What was the reason for the -libraries change in 18d? > > The change was made in order to allow require to work as is to load > the implementation-supplied libraries, i.e. CLX, CLM, gray-streams, > etc. [snip]
Would it be useful/desirable to put a user-definable hook function in modules.lisp so that if (require 'foo) fails to load foo-library.x86f, the user-defined hook function gets called to see what it can do? This would be a bit more general than the defmodule mechanism in place, and could work alongside it, and would allow users to arrange their require'able libraries whereever they want, with whatever naming convention they want. Also, I think I've found what appears to be a trivial docstring error in 18d: the doc string for require in modules.lisp says '*load-verbose* is bound to *require-verbose* which defaults to NIL' but in fact modules.lisp has (defvar *require-verbose* t) __________________________________________________ Do you Yahoo!? HotJobs - Search new jobs daily now http://hotjobs.yahoo.com/
