April 2015 - asdf-devel - mailman3.common-lisp.net

Test failure on ABCL, Mac OSX
by Robert Goldman 08 Apr '15

08 Apr '15

test-encodings fails for me on ABCL 1.1.1 I believe that this is a long-standing failure, yes? Best, r

2 2

[asdf-devel] Fixing asdf-system-connections
by Liam Healy 08 Apr '15

08 Apr '15

I am using asdf-system-connections and notice a glitch in its design. As the original author no longer maintains it, I'm try to fix this myself. This system is designed to allow the loading of a connected system (say "A") automatically when two or more dependent systems (say "B" and "C") are loaded. The problem I'm encountering is that when another system (say "D") is defined to depend on B and C, then A is not loaded until after D is done loading, but D may need the definitions in A. asdf-system-connections defines a function load-connected-systems which does the work of loading the connected system definitions, but this is called from a new #'operate :after method which apparently doesn't get called until A is done loading. I am looking for a place from which to call load-connected-systems that will trigger its call as soon as it's able, i.e., immediately once both "B" and "C" are loaded. I'm not familiar with the internals of ASDF and wonder if someone can guide me to a good place to define this. Thanks, Liam

2 1

[asdf-devel] Small testing convenience pushed
by Robert P. Goldman 08 Apr '15

08 Apr '15

If you test on ACL with the many variations that Dave set up (thanks, Dave!), there is a new problem: you end up testing upgrade over and over and over and over, and it takes forever. This recent commit adds the ability to set ASDF_TEST_UPGRADE_LISPS, typically as a subset of ASDF_TEST_LISPS. If the variable is unset, it should not affect you (but this is not tested). Best, r

1 0

[asdf-devel] ASDF walkthrough
by Faré 08 Apr '15

08 Apr '15

Dear Lisp hackers, I'm considering recording a walk through the ASDF sources. I'd like to have an interactive session over Google Hangout with one or a few people, explaining the current code in asdf/defsystem (i.e. not going into uiop, except to minimally explain what asdf uses). That should take about 2 hours. To enjoy the walkthrough, you need to be somewhat fluent in Common Lisp, and somewhat familiar with how to use ASDF, though not necessarily with either extending it or hacking its internals. If at least one person is familiar with ASDF 2 and has questions, that could be interesting, or that could be a separate session. Please respond me to this email (privately or publicly) if you're interested. —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org We are always in anarchy. But we pay a hefty price maintaining the illusion that we aren't, and another one being misled by the illusion.

2 2

[asdf-devel] Yes proglogue and epilogue is used!
by Jean-Claude Beaudoin 08 Apr '15

08 Apr '15

Hello Faré, Yes the prologue and epilogue is (or will be, in the publicly and officially sanctioned ASDF-way once I send you my small MKCL mods for ASDF 3) used after all. Maybe not really by ECL, although it should, but by MKCL. It is an essential part of the program-op processing. You are right about the fact that prologue and epilogue are not very well designed as they stand in ECL (and how MKCL inherited them from ECL). But they really make sense if they are considered in the context of #'compiler:build-program. I would even say that they are essential in the context of #'compiler:build-program. I am currently putting the finishing touch to ASDF 3.0.3 on MKCL 1.1.7 on Windows (3 more tests to fix). I should be done somewhat shortly and after that I'll sent the ASDF list what I have got, merged with ASDF head. Sorry if I could not reply to your ecls-list messages more promptly but I was out all day participating in a double fencing tournament. I did basically a somewhat marathon-like 8 hours straight of competitive épée, so I hope you will understand if I stand a bit out of phase with my computer keyboard for a few more hours while I try to recover. Cheers, Jean-Claude Beaudoin

2 1

[asdf-devel] Patch for UIOP/UTILITY:ENSURE-FUNCTION
by Mark Evenson 08 Apr '15

08 Apr '15

Without the attached patch, I believe the use of a function for output translations is hosed from post asdf-3.0.2 onwards. I think ABCL is the only implementation actively using the ability to specify an output translation as a function, as indeed Faré expressly introduced this for us. ABCL uses a specialized output translation to translate the location of FASLs for ASDF systems stored in jar files (like ABCL’s contribs) which can’t otherwise be expressed in the translation DSL. I have [committed an asdf-3.0.3.0.1 including this patch][r14583] to ABCL trunk, which I will sync in the near future to ASDF master if this is indeed the correct way to patch the problem. [r14583]: http://abcl.org/trac/changeset/14583 -- "A screaming comes across the sky. It has happened before but there is nothing to compare to it now."

1 0

[asdf-devel] Moderation becoming a problem
by Robert P. Goldman 08 Apr '15

08 Apr '15

I know that "everything in moderation" is a virtue, but "moderating everything" is burdensome. I was glad to see so much interest in the ASDF package, and the corresponding urge to participate in the recent discussion about defining symbols in the keyword package, but if you want to participate in an ongoing discussion, please sign up for the mailing list. Especially with the new, unimproved cl.net mailing list software, moderating a large number of non-member posts is a nuisance. Thanks!

1 0

[asdf-devel] Re: ASDF walkthrough
by Faré 08 Apr '15

08 Apr '15

I put my recording of the ASDF Walkthrough on Youtube. It's nothing great, but oh well, it's as good an introduction to the code as you'll get (for now). It's long, but you can watch at x1.5 speed for reduced bore — or use youtube-dl then vlc to watch at whichever speed you prefer. https://www.youtube.com/watch?v=Qqqbc31ZZ-U The various cleanups suggested during the talk were committed; they were all valid: the testing errors during the session were due to modifying the files while they were being tested. ASDF 3.1.0.60 passes all tests for me. I think Robert has some more comments to add to the code and things to add to the documentation, but I believe that codewise it might already be a release candidate, so please test! —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org "The Army is a place where you get up early in the morning to be yelled at by people with short haircuts and tiny brains." — Dave Barry

1 0

[asdf-devel] 3.0.3 release plans
by Robert P. Goldman 08 Apr '15

08 Apr '15

I was hoping to release this past week, but was unable to get further testing done. Before releasing, I try to test a number of large systems that we use here at SIFT with the latest ASDF. This provides a real world add-on to the test suite. Unfortunately, I have not had a chance to make this test. I hope to do so in the next couple of days. That should either reveal bugs, or lead to an immediate release of 3.0.3. It would be great if the quicklisp issues could be resolved satisfactorily in time for 3.0.3. Best, r

3 3

[asdf-devel] New ASDF test failures
by Robert P. Goldman 08 Apr '15

08 Apr '15

CCL: package-system-test.script clisp: asdf-pathname-test.script package-system-test.script test-sysdef-asdf.script sbcl: package-system-test ecl: package-system-test.script test-bundle.script (expected) test-sysdef-asdf.script cmucl: package-system-test lispworks: package-system-test I'm stopping for now -- it seems like package-system-test is now portably broken, at least on Mac OSX. Happy New Year, r

2 5