-
- Downloads
Be a little bit more defensive about looking up classes for component
types. It seems regrettably common for system authors, despite the documentation, to place their system in CL-USER, where the user can quite legitimately add symbols. Adjust the lookup code in CLASS-FOR-TYPE to ignore symbols not naming subclasses of ASDF:COMPONENT, and also to try the symbol itself first if it's not a keyword. Also adjust the documentation slightly to make this slightly clearer. Add test files, and make the clisp test-harness work for me.
test/test-package.asd
0 → 100644
test/test-package.script
0 → 100644
Please register or sign in to comment