14 Jun
2011
14 Jun
'11
2:29 p.m.
David Lichteblau david@lichteblau.com writes:
Quoting Zach Beane (xach@xach.com):
David Lichteblau david@lichteblau.com writes:
Quoting Zach Beane (xach@xach.com): [...]
What's the :type :unspecific for? It seems to work on CLISP (and all other implementations I tried) without it; is it a precaution against a *default-pathname-defaults* that apparently has a value for :type?
I don't know. Here's the snippet from the patch submitter, can you make sense of it? Perhaps only very old asdf2 has this problem?
Yes, that looks like it's the case to me. ASDF2 no longer behaves like he describes.
Does this change work for you on clisp?
[snip]
CLISP compiles it without complaint with that change.
Zach