While I don't have clear numbering plans for ASDF post 2.0,
my plan until we reach 2.0 is that I will try to get near 1.x00 when a
major feature is added.
We're currently at 1.601. It is hopefully stable enough for
implementors to use. At least that's the intent. But it is not yet
extensively
On Thu, Feb 4, 2010 at 9:23 AM, Faré fah...@gmail.com wrote:
And so, regarding ECL: please upgrade ASDF to 1.601 if you can. It
would be nice. And reduce the asdf self-upgrade strictures.
The point is that I upgraded to 1.596 on Samium's request and assurance that
it works with ECL, and now
On Thu, Feb 4, 2010 at 7:50 PM, Faré fah...@gmail.com wrote:
ASDF didn't use to support ECL for testing at all. I just added this
support and found about the warnings, so it counts as my having warned
you immediately.
How can I run the tests? run-tests.sh is not working for me.
Juanjo
--
On 2/4/10 Feb 4 -2:29 PM, Juan Jose Garcia-Ripoll wrote:
On Thu, Feb 4, 2010 at 7:50 PM, Faré fah...@gmail.com
mailto:fah...@gmail.com wrote:
ASDF didn't use to support ECL for testing at all. I just added this
support and found about the warnings, so it counts as my having warned
If it's the compile-asdf script hanging instead of exiting, I just
pushed 1.603 that has a fix for running tests in ECL w/o manual
intervention. My apologies. (No functional change to asdf itself, only
to the test script infrastructure.)
[ François-René ÐVB Rideau | ReflectionCybernethics |
On Thu, Feb 4, 2010 at 9:49 PM, Faré fah...@gmail.com wrote:
If it's the compile-asdf script hanging instead of exiting, I just
pushed 1.603 that has a fix for running tests in ECL w/o manual
intervention. My apologies. (No functional change to asdf itself, only
to the test script
