Hello,
can somebody explain to me what is the :require dependency specification, and how it compares to just a simple-component-name ?
Thanks.
On 6/25/15 Jun 25 -4:20 PM, Didier Verna wrote:
Hello,
can somebody explain to me what is the :require dependency specification, and how it compares to just a simple-component-name ?
Thanks.
According to the manual REQUIRE-SYSTEM is "... a version of @code{load-system} that skips trying to update systems that are already loaded."
There is no REQUIRE-OP.
There is a REQUIRE-SYSTEM which is a system whose loading is handled by REQUIRE instead of native ASDF.
When you make a :REQUIRE dependency, the corresponding system is made into a REQUIRE-SYSTEM so that when you try to operate on it, the operations are handled by REQUIRE instead of ASDF proper.
This might be useful, e.g., on ACL, which has many bundled modules which are loaded by REQUIRE.
I'm not sure there is a common implementation-independent use case, since people aren't distributing a lot of code to be loaded with REQUIRE, AFAICT.
Hope that helps. Sorry for the late answer: we've been grappling with some knotty bugs on Windows.
Cheers, r
Robert Goldman rpgoldman@sift.net wrote:
According to the manual REQUIRE-SYSTEM is "... a version of @code{load-system} that skips trying to update systems that are already loaded."
There is no REQUIRE-OP.
There is a REQUIRE-SYSTEM which is a system whose loading is handled by REQUIRE instead of native ASDF.
OK, this is what I figured in the meantime. But then, this seems to contradict what the manual says (the part you're mentioning above).
This might be useful, e.g., on ACL, which has many bundled modules which are loaded by REQUIRE. I'm not sure there is a common implementation-independent use case, since people aren't distributing a lot of code to be loaded with REQUIRE, AFAICT.
I guess it's mostly useful for implementation-specific libraries. I use it for sb-grovel for instance.
Hope that helps. Sorry for the late answer: we've been grappling with some knotty bugs on Windows.
No worries. When I have bugs on windows, I usually close the blinds :-D
On 6/29/15 Jun 29 -9:26 AM, Didier Verna wrote:
Robert Goldman rpgoldman@sift.net wrote:
According to the manual REQUIRE-SYSTEM is "... a version of @code{load-system} that skips trying to update systems that are already loaded."
There is no REQUIRE-OP.
There is a REQUIRE-SYSTEM which is a system whose loading is handled by REQUIRE instead of native ASDF.
OK, this is what I figured in the meantime. But then, this seems to contradict what the manual says (the part you're mentioning above).
Yes, Faré points out that it's confusing that we use the word REQUIRE both for "the thing we do when we process a REQUIRE dependency" and for REQUIRE-SYSTEM which is "LOAD-SYSTEM but with limits on the loading of dependencies."
Cheers, r
-
Didier Verna -
Robert Goldman