2 Jul 2002 04:50
ASDF system for portable allegroserve on CMUCL
David Lichteblau <david <at> lichteblau.com>
2002-07-02 02:50:35 GMT
2002-07-02 02:50:35 GMT
[cc'ed to the cclan people, please respond to the appropriate address] I am too stupid to compile paserve using defsystem on CMUCL, so I have made ASDF systems replacing the old CMUCL systems which essentially do the same thing but happen to work. (Sorry -- I'm too dumb and lazy to figure out what the defsystem problems are about, but interested in having a ASDF version anyway...) (The attached patch also changes client.cl to use HTTP/1.0 instead of 1.1 as a default on CMUCL, since 1.1 requires chunked encoding, which is not yet supported on CMUCL.) Perhaps someone finds this useful, David -- -- FAILURE IS NOT AN OPTION - it comes bundled with the software.
As to the more general issue: how much of a problem is it really to
mandate that the tarball name is the same as (or mechanically
derivable from) the asdf system name? I've been saying all along that
David Lichteblau <david <at> lichteblau.com> writes:
> Are compilers obliged to signal an error if there are errors in the
> sources?
No. According to 3.2.5, COMPILE-FILE may or may not catch errors
signalled during the compilation process. And for your real-life
example, CMUCL does, SBCL doesn't.
There are a couple of points worth making in connection with asdf.
Neither solves your problem, but either may at least ameliorate it
slightly.
1) you can set ``:on-failure :warn'' on individual components, instead
of having to use the same *compile-file-failure-behaviour* across
the whole system. This will work with CMUCL because it stops on
compile errors anyway. It doesn't help with SBCL
2) for interactive development, the (badly named, I now realise)
SKIP-COMPONENT restart can be used to carry on after an error that
the user knows was not important.
For a proper fix there are three things I'd like to look at
RSS Feed