In the past, to introduce changes a fraction as compatibility-breaking
(e.g. making utf-8 the default, or changing the internals of OPERATION), I
would write up an explanation why the change is desired that anyone can
read, discuss on the mailing list, write the code but keep it unmerged or
Oh, and as for binding variables around files, this has subtly different
meanings when compiling a file, loading its fasl or loading its source. And
if done wrong it can easily break fasl concatenation or linking on ecl and
mkcl, where you just can't bind around the loading of individual fasls,
I think this is still true, but... we cannot be discussing ASDF 3.2.1
here. It was released almost 7 years ago, and for whatever reason Zach
refuses to update. The current version is 3.3.7
Please get a more recent ASDF and try again. I *believe* that this
behavior is still in place: Faré
