[asdf-devel] News on the front
![](https://secure.gravatar.com/avatar/0345f6261d6ced21145afdec166fd114.jpg?s=120&d=mm&r=g)
Dear Lisp hackers, I've completed yet another major pass of refactoring of ASDF. It is now divided into many files, that are concatenated together for single-file delivery. (An idea that I once rejected when James Anderson proposed it 3 years ago; he might have known better. The file has more than quadrupled in size since.)
From a pristine git checkout, you can concatenate them from the command-line with make build/asdf.lisp or from lisp with a recent bootstrapped asdf.lisp with (asdf:operate 'asdf::concatenate-source-op :generate-asdf)
About 45% of ASDF is utilities, and those are now available through a semi-independent system asdf-driver. See make wc wc-driver wc-asdf. I'have notably moved in run-program/ from xcvb-driver, and its native-namestring support, by popular demand, which increased this number. I brought in the condition-control code and image support from xcvb-driver as well; I'll be working to package them better. Hot upgrade is preserved through the heroic development of define-package, an extension to defpackage that makes things as declared from however they were, instead of throwing an error at the first discrepancy. You better know what you want. As a result from this and all the package declarations, plus the bundle and concatenate support, ASDF has swollen 60% in size since 2.26, or 42% since I merged in asdf-bundle in 2.26.7. I'll argue that the functionality is also much improved, including the fixing of the fundamental build model that I've discussed in previous emails. I won't release anything until all the packages in quicklisp work, and I'll have to install cl-test-grid for that, but I invite those of you who are interested to test it and/or comment on the changes. It looks like I mostly understand ASDF these days. —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org Every technique is first developed, then used, important, obsolete, normalized, and finally understood.
![](https://secure.gravatar.com/avatar/9342d16e648d947803f4af8f1e6a4871.jpg?s=120&d=mm&r=g)
"Fare" == Far <Far> writes:
Fare> Dear Lisp hackers, I've completed yet another major pass of Fare> refactoring of ASDF. It is now divided into many files, Fare> that are concatenated together for single-file delivery. Fare> (An idea that I once rejected when James Anderson proposed Fare> it 3 years ago; he might have known better. The file has Fare> more than quadrupled in size since.) From a pristine git Fare> checkout, you can concatenate them from the command-line Fare> with Fare> make build/asdf.lisp Fare> or from lisp with a recent bootstrapped asdf.lisp with Fare> (asdf:operate 'asdf::concatenate-source-op Fare> :generate-asdf) Is the plan that asdf is still delivered as one giant file or will it eventually move to being delivered as multiple files? Just curious. Ray
![](https://secure.gravatar.com/avatar/0345f6261d6ced21145afdec166fd114.jpg?s=120&d=mm&r=g)
On Fri, Jan 11, 2013 at 12:26 PM, Raymond Toy <toy.raymond@gmail.com> wrote:
Is the plan that asdf is still delivered as one giant file or will it eventually move to being delivered as multiple files?
Just curious.
ASDF will still be delivered as one giant file. That's what makes sense for bootstrap purposes. —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org Instead of loving your enemies, treat your friends a little better. — Edgar Watson Howe
![](https://secure.gravatar.com/avatar/9342d16e648d947803f4af8f1e6a4871.jpg?s=120&d=mm&r=g)
"Fare" == Far <Far> writes:
Fare> On Fri, Jan 11, 2013 at 12:26 PM, Raymond Toy Fare> <toy.raymond@gmail.com> wrote: >> Is the plan that asdf is still delivered as one giant file or >> will it eventually move to being delivered as multiple files? >> >> Just curious. >> Fare> ASDF will still be delivered as one giant file. That's what Fare> makes sense for bootstrap purposes. Sounds good. Thanks, Ray
![](https://secure.gravatar.com/avatar/b053ca7abf2716d9df3ce01278d60947.jpg?s=120&d=mm&r=g)
On 1/11/13 5:53 PM, Faré wrote:
Dear Lisp hackers,
I've completed yet another major pass of refactoring of ASDF.
[…] Coolness! Keep it coming! Failing to compiled the concatenated fasl from ASDF master tip (local : UNDEFINED-FUNCTION: ;COMMON-LISP:CELL-ERROR-NAME triggers autoloading of org.armedbear.lisp.cell_error_name ... ; Autoloaded org.armedbear.lisp.cell_error_name (0.0050 seconds) The function ASDF/PACKAGE::WHEN-FISHY is undefined. Have I missed some packaging in the implemenation (abcl-1.2.0-dev)? ABCL trunk currently has some problems with autoloading (some) COMMON-LISP functions via SETF expanders, which I am in the process of fixing. ; SLIME 2012-11-23 CL-USER> (lisp-implementation-version) "1.2.0-dev" "Java_HotSpot(TM)_64-Bit_Server_VM-Sun_Microsystems_Inc.-1.6.0_37-b06" "amd64-SunOS-5.11" Thanks, Mark <evenson@panix.com>
![](https://secure.gravatar.com/avatar/0345f6261d6ced21145afdec166fd114.jpg?s=120&d=mm&r=g)
Dear Mark, On Tue, Jan 15, 2013 at 6:35 AM, Mark Evenson <evenson@panix.com> wrote:
On 1/11/13 5:53 PM, Faré wrote:
Dear Lisp hackers,
I've completed yet another major pass of refactoring of ASDF.
[…]
Coolness! Keep it coming!
Thanks for the appreciation. Maybe some day you can help me better integrate your ASDF-JAR into ASDF.
Failing to compiled the concatenated fasl from ASDF master tip (local :
UNDEFINED-FUNCTION: ;COMMON-LISP:CELL-ERROR-NAME triggers autoloading of org.armedbear.lisp.cell_error_name ... ; Autoloaded org.armedbear.lisp.cell_error_name (0.0050 seconds) The function ASDF/PACKAGE::WHEN-FISHY is undefined.
there is a bug in ABCL, that fails to expand a macrolet around a defun. My workaround is to nest the macrolet inside the defun; this is made possible by my not having broken the defun into multiple functions as originally intended; otherwise, I suppose I could have a defmacro with a long name, or just trusted package discipline. Regards, —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org Economic illiteracy often leads one to take for wealth creation or cost reduction what is only a forced displacement of activity, with no primary gain, and a lot of secondary costs and negative side-effects. — Faré
participants (3)
-
Faré
-
Mark Evenson
-
Raymond Toy