asdf-devel March 2013

asdf-devel@common-lisp.net

15 participants
23 discussions

[asdf-devel] ASDF 2.30 released
by Faré 02 Mar '13

02 Mar '13

Dear Lisp hackers, ASDF 2.30 is another stability release in preparation for ASDF 3. Since 2.29, in addition to specific portability fixes for CCL and CMUCL, it notably restores some backward compatible behavior for syntax tables around loading .asd files, using mutable global tables, instead of standard syntax tables. Just like 2.29, 2.28 and 2.27 before it, ASDF 2.30 is a pre-release of ASDF 3, an almost complete rewrite of ASDF, and includes a vast number of improvements since ASDF 2.26. http://lists.common-lisp.net/pipermail/asdf-announce/2013-February/000014.h… We invite all implementation vendors to update to ASDF 2.30. We also invite all implementations to make the standard *readtable* and *print-pprint-dispatch* tables immutable, with useful error messages when a modification is attempted. See how the CLHS forbids conformant programs from modifying them: http://clhs.lisp.se/Body/26_glo_s.htm#standard_readtable http://clhs.lisp.se/Body/26_glo_s.htm#standard_pprint_dispatch_table Such modification can only result in problems down the line for users, and it would be nice if at least when SAFETY isn't 0, that were checked. In some unspecified future, we'd like to revert to ASDF 2.29's behavior of binding the syntax tables to their standard values, and then we hope that most implementations will immediately catch misguided attempts by users to modify them (SBCL is the only implementation enforced immutability on both tables). Many thanks to stassats and avodonosov for their help in testing ASDF and helping make it more robust, more portable and more backward compatible. —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org There is no reason ever to have the same thought twice, unless you like having that thought — David Allen, "Getting Things Done"

2 2

[asdf-devel] Is is possible to not have ASDF output build-report files and foo.bar-warnings files?
by Gary King 02 Mar '13

02 Mar '13

An admittedly quick look at the source didn't ring any bells for me. thanks, -- Gary Warren King, metabang.com Cell: (413) 559 8738 Fax: (206) 338-4052 gwkkwg on Skype * garethsan on AIM * gwking on twitter

2 2

[asdf-devel] clearing output-translations for a "dumped" image
by Dave Cooper 01 Mar '13

01 Mar '13

Dear All, When "saving a world" (i.e. "dumping" an image, e.g. "dumplisp" in Allegro CL), which has asdf (and quicklisp) loaded in it, what is the proper way to clear the output-translations and any other local path residue from ending up in the saved image? That is, when a new user starts the image on a target machine, it should be forced to re-initialize the output-translations to the appropriate path for the new user (e.g. ~/.cache/common-lisp/... with respect to new user's home directory). -- My Best, Dave Cooper, Genworks Support david.cooper(a)genworks.com, dave.genworks.com(skype) USA: 248-327-3253(o), 1-248-330-2979(mobile) UK: 0191 645 1699

3 6

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

asdf-devel March 2013