On 2009-09-23, at 08:59 , james anderson wrote:
On 2009-09-23, at 08:12 , Daniel Herring wrote:
[...]
My view is that, if an implementation provides a supported hook to augment REQUIRE, then ASDF should take advantage of that hook. Otherwise, ASDF's users are left passing these around on the black market.
People who really don't want that behavior could (push :disable-asdf-require-hook *features*) before loading ASDF...
could this please at least be duplicated to a variable which has the equivalent effect on the function's actions.
r.goldman observed, that my concern may not be self-evident.
one would expect the reader conditionalization to be limited to the vendor-specific hooks, while the operator's generic behavior is left to execution-time controls.
the execution-time control is necessary if the user is to effect the function's behavior in those cases where the vendor has supplied a compiled version of the asdf package.
- Daniel
asdf-devel mailing list asdf-devel@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel
asdf-devel mailing list asdf-devel@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel