can you run the below tests, in order or priority?
1- Can you test what is currently in master, a.k.a. 188.8.131.52, as a
release candidate for 3.3.2? It has been too long since 3.3.1 was
released with several bugs that have impacted Quicklisp users.
2- Can you test what is currently in the syntax-control branch as a
release candidate for 3.3.3 or 3.4.0? We want to merge syntax
but it's a significant enough change that we don't want it at the
time as the bug fixes. Also...
3- Can you test what is currently in the syntax-control branch as a
release candidate for 3.3.3 or 3.4.0, but with the following
just after you load asdf but before you start using it:
uiop:*shared-readtable* (copy-readtable nil)) ? Indeed, we want to
what breaks if we disable extensions implementation-specific reader
extensions. Test most important on CCL. I don't expect much breakage
on other implementations, but it may exist, too.
4- While you're at it, can you also run the test, at least on sbcl,
with (defparameter uiop:*shared-readtable*
? This will detect what breaks when we make the default readtable
The thing is, we really want to have this syntax control, but we
want to preserve backward compatibility, and we can't make asdf
stricter until every client is fixed (famous last word; of course we
failed at exactly that in 3.3.1 — we could build correctly, but
also spuriously rebuild if secondary systems were misnamed; fixed in
—♯ƒ • François-René ÐVB Rideau
A friend once asked me if I had ever considered terrorism as a means
political change. I replied that yes, I had considered it... and
Because it only causes change for the worse.
Killing innocent people does not promote a culture of peaceful