Thread view

Dear Lisp hackers,
as things have settled down, ASDF is resuming a monthly release schedule.
Therefore I am glad to announce ASDF 2.33.
Please update your implementations, your distributions, etc.,
after suitable testing.
Since previous release 2.32, it includes the following changes:
* Portability tweaks for ABCL, Allegro, CCL, CLISP, ECL, LispWorks, SBCL.
* deferred-warning received yet more improvements for CCL.
* upgrade is made more robust in many cases, notably for ECL, SBCL,
or when using UIOP with an old ASDF<=2.26.
* Packages have been tweaked to pass more tests,
notably wrt what symbols are exported.
* Image lifecycle support is improved, thanks to deploying ASDF3 for QRes.
More options for dump-image on CCL; handle reentrance in restore-image.
* delete-directory-tree, delete-empty-directory, copy-file,
directory-exists-p, file-exists-p were added to UIOP,
also better strcat, with reduce/strcat, base-string-p, etc.
* Recompilation avoided for things already done by defsystem-depends-on.
* monolithic-fasl-op was fixed in cases when the main system has components.
* fasl-op and monolithic-fasl-op now work on ABCL trunk and upcoming 1.2.0,
and will eventually replace the ABCL-JAR contrib.
* *uninteresting-conditions* was added as a common list of conditions
shared between the compile-time and load-time muffled conditions.
Thanks a lot the many hackers who helped with this release, including
Stas Boukarev, Gary Byers, Dave Cooper, Mark Evenson, Robert Goldman,
Erik Huelsman, Alejandro Sedeño, Martin Simmons, Anton Vodonosov
(and my apologies if I forgot your name in this list).
—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org
Mail addiction is a malediction.

Faré <fahree@...> writes:
> Dear Lisp hackers,
>
> as things have settled down, ASDF is resuming a monthly release schedule.
> Therefore I am glad to announce ASDF 2.33.
> Please update your implementations, your distributions, etc.,
> after suitable testing.
>
> Since previous release 2.32, it includes the following changes:
>
> * Portability tweaks for ABCL, Allegro, CCL, CLISP, ECL, LispWorks, SBCL.
>
> * deferred-warning received yet more improvements for CCL.
>
> * upgrade is made more robust in many cases, notably for ECL, SBCL,
> or when using UIOP with an old ASDF<=2.26.
>
> * Packages have been tweaked to pass more tests,
> notably wrt what symbols are exported.
>
> * Image lifecycle support is improved, thanks to deploying ASDF3 for QRes.
> More options for dump-image on CCL; handle reentrance in restore-image.
>
> * delete-directory-tree, delete-empty-directory, copy-file,
> directory-exists-p, file-exists-p were added to UIOP,
> also better strcat, with reduce/strcat, base-string-p, etc.
>
> * Recompilation avoided for things already done by defsystem-depends-on.
>
> * monolithic-fasl-op was fixed in cases when the main system has components.
>
> * fasl-op and monolithic-fasl-op now work on ABCL trunk and upcoming 1.2.0,
> and will eventually replace the ABCL-JAR contrib.
>
> * *uninteresting-conditions* was added as a common list of conditions
> shared between the compile-time and load-time muffled conditions.
*uninteresting-conditions* value on SBCL is really bad:
(sb-c::simple-compiler-note
"&OPTIONAL and &KEY found in the same lambda list: ~S"
#+sb-eval sb-kernel:lexical-environment-too-complex
sb-kernel:undefined-alien-style-warning
sb-grovel-unknown-constant-condition ; defined above.
;; sb-ext:implicit-generic-function-warning ; Controversial. Let's allow it by default.
sb-int:package-at-variance
sb-kernel:uninteresting-redefinition
;; BEWARE: the below four are controversial to include here.
sb-kernel:redefinition-with-defun
sb-kernel:redefinition-with-defgeneric
sb-kernel:redefinition-with-defmethod
sb-kernel::redefinition-with-defmacro)
It made me miss several problems within my code, because it silently ate
redefinition warnings. And other conditions are interesting too, they
are signalled for a reason. I just set *uninteresting-conditions* to
NIL. ASDF goes to lengths to deliver undefined warnings, but then just
ignores equally important redefinition warnings or undefined alien
warnings.
I really wouldn't want an ASDF version, which defeats all the provisions
to ease development and debugging, included with SBCL.
--
With best regards, Stas.

I admit I copy/pasted the list of muffled warnings from a large
project at work, where we needed it to silence all the many libraries
we used and our code, too.
If the consensus is that the default value should be NIL, I'll use
that for my next release 2.34.
I believe these might deserve to be included by default:
(sb-c::simple-compiler-note ;; most users don't care about these for
other people's libraries
"&OPTIONAL and &KEY found in the same lambda list: ~S" ;; also a pain
#+sb-eval sb-kernel:lexical-environment-too-complex ;; this is is just noise
;; sb-kernel:undefined-alien-style-warning ;; I load my .so's after
I build, but to each his own.
sb-grovel-unknown-constant-condition ;; or else depends-on :sb-posix is noisy.
;; sb-ext:implicit-generic-function-warning ; Controversial. Let's
allow it by default.
;; sb-int:package-at-variance ; I find it a pain when recompiling
some libraries
sb-kernel:uninteresting-redefinition ;; the name suggests it should
be included by default
)
If the current value of *uninteresting-conditions* is a show-stopper
for upgrading the asdf in sbcl, I can make said release happen now.
—♯ƒ • 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.
On Thu, Apr 4, 2013 at 5:05 AM, Stas Boukarev <stassats@...> wrote:
> Faré <fahree@...> writes:
>
>> Dear Lisp hackers,
>>
>> as things have settled down, ASDF is resuming a monthly release schedule.
>> Therefore I am glad to announce ASDF 2.33.
>> Please update your implementations, your distributions, etc.,
>> after suitable testing.
>>
>> Since previous release 2.32, it includes the following changes:
>>
>> * Portability tweaks for ABCL, Allegro, CCL, CLISP, ECL, LispWorks, SBCL.
>>
>> * deferred-warning received yet more improvements for CCL.
>>
>> * upgrade is made more robust in many cases, notably for ECL, SBCL,
>> or when using UIOP with an old ASDF<=2.26.
>>
>> * Packages have been tweaked to pass more tests,
>> notably wrt what symbols are exported.
>>
>> * Image lifecycle support is improved, thanks to deploying ASDF3 for QRes.
>> More options for dump-image on CCL; handle reentrance in restore-image.
>>
>> * delete-directory-tree, delete-empty-directory, copy-file,
>> directory-exists-p, file-exists-p were added to UIOP,
>> also better strcat, with reduce/strcat, base-string-p, etc.
>>
>> * Recompilation avoided for things already done by defsystem-depends-on.
>>
>> * monolithic-fasl-op was fixed in cases when the main system has components.
>>
>> * fasl-op and monolithic-fasl-op now work on ABCL trunk and upcoming 1.2.0,
>> and will eventually replace the ABCL-JAR contrib.
>>
>> * *uninteresting-conditions* was added as a common list of conditions
>> shared between the compile-time and load-time muffled conditions.
>
> *uninteresting-conditions* value on SBCL is really bad:
> (sb-c::simple-compiler-note
> "&OPTIONAL and &KEY found in the same lambda list: ~S"
> #+sb-eval sb-kernel:lexical-environment-too-complex
> sb-kernel:undefined-alien-style-warning
> sb-grovel-unknown-constant-condition ; defined above.
> ;; sb-ext:implicit-generic-function-warning ; Controversial. Let's allow it by default.
> sb-int:package-at-variance
> sb-kernel:uninteresting-redefinition
> ;; BEWARE: the below four are controversial to include here.
> sb-kernel:redefinition-with-defun
> sb-kernel:redefinition-with-defgeneric
> sb-kernel:redefinition-with-defmethod
> sb-kernel::redefinition-with-defmacro)
>
> It made me miss several problems within my code, because it silently ate
> redefinition warnings. And other conditions are interesting too, they
> are signalled for a reason. I just set *uninteresting-conditions* to
> NIL. ASDF goes to lengths to deliver undefined warnings, but then just
> ignores equally important redefinition warnings or undefined alien
> warnings.
>
> I really wouldn't want an ASDF version, which defeats all the provisions
> to ease development and debugging, included with SBCL.
>
> --
> With best regards, Stas.