From: Liam M. H. <Lia...@nr...> - 2002-11-25 18:48:29
|
>>>>> "Marco" == Marco Antoniotti <ma...@cs...> writes: >> From: "Liam M. Healy" <Lia...@nr...> >> In one of my systems, I have a few files whose definitions are >> infrequently used and that are time-consuming to load. I would like >> to make them optionally load under defsystem-3.x: they would compile >> with the rest of the system, but would only be loaded with an explicit >> command. I do not want to make them a separate system because I want >> to keep them associated with this system. Is there a way to do this >> easily in the defsystem structure? Marco> The way I do it is the group these files into a separate :module with Marco> no (or only few) dependencies. Marco> This way you get compilation and loading of these files only at Marco> specific times. E.g. Marco> (mk:defsystem "FOO" Marco> :components ("base" Marco> (:module "load-sparingly" Marco> :source-pathname "where/they/are/" Marco> :components ("f1" "f2")) Marco> (:file "x" Marco> :depends-on ("base" "load-sparingly")))) Marco> ... I think you get the idea. Actually, I don't get the idea. This looks like an ordinary system definition with three pieces, "base", "load-sparingly" and "x", that will load when the system loads. How do you prevent the automatic loading of a piece, "load-sparingly" presumably? How do you trigger its loading manually? Liam |