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

[asdf-devel] Is there anything one can do to make old versions of clisp run ASDF2?
by Robert Goldman 01 Sep '10

01 Sep '10

I am getting complaints about a library that I maintain, which is loaded using ASDF, from CLISP users. These aren't bugs with my system, but when they try to bring up ASDF to load it... fail. This has to do with this error: #<PACKAGE POSIX> has no external symbol with name "UID" I believe there is a CLISP ticket about this. The problem is that the version of CLISP distributed with Ubuntu 10.4 and the one distributed with OpenSUSE 11.2 both are too old to have this fix. It seems like it would be A Good Thing if ASDF2 could be made compatible with Ubuntu and OpenSUSE. Is there an easy work-around for this that we could patch into the current version of ASDF2? Cheers, r

2 1

[asdf-devel] Optional dependencies
by Tobias C Rittweiler 21 Aug '10

21 Aug '10

Quite a few libraries come with reader hacks. They usually come with a ENABLE-FOO-SYNTAX function. I'd like those libraries to optionally depend on the named-readtables library, and define a named readtable that includes their hacks. So users can just use (IN-READTABLE FOO:SYNTAX) on a per-file basis. What do you think would be the best way to do it? There's :weakly-depends-on which only loads a dependency if that system is present. Named-readtables pushes :NAMED-READTABLE to *FEATURES*. So in principle, people can use (:weakly-depends-on :named-readtables) and then #+named-readtables (named-readtables:defreadtable ...) Or put that definition in a file readtable.lisp and use feature-conditionalized compilation in the system definition (which used to be, and I guess still is, awfully awkward -- I never remember how to do it.) Now I'm wondering how good that solution is. What is if the library was compiled with a core that happened to include named-readtables? Trying to load that fasl with another core file would probably result in an obscure error. Now, it's a shoot-yourself-in-the-foot kind of thing to do, but I'd think it's something that can happen quite easily. Does ASDF somehow guard against this case? >From what I can see, it appears that :WEAKLY-DEPENDS-ON was added in a quick rush thinking that it might be appropriate for conditional compilation, but it really is not. Does that seem true to you, too? Maybe people can share how they got bitten by it? I'd think ASDF should include a ./configure step (there are extension for that kind of thing out there), and should then save configuration choices persistently, and check for these when loading a system. -T. PS. Thanks, appreciation, and kudos again to Fare and Robert for having taken up the ASDF hat.

5 8

Re: [asdf-devel] [Sbcl-help] cl-fad, sb-grovel and failure to compile constants.lisp-temp
by Nikodemus Siivola 18 Aug '10

18 Aug '10

On 18 August 2010 14:49, James Fleming <lisp(a)electronic-quill.net> wrote: > The very short version of the question: what changed between 1.0.39 and > 1.0.40, regarding the expected locations of source files, and when/how > they're expected to be copied there during asdf::perform operations? ASDF version supplied with SBCL changing is the probable culprit for at least some of this -- adding asdf-devel to CC. (It seems the NEWS entry for ASDF2 was forgotten, oops...) However, this bit right here > ; compiling file > "/opt/pkgs/sbcl-1.0.41/lib/sbcl/sb-grovel/def-to-lisp.lisp" (written 15 indicates that something else is wrong too: loading SB-GROVEL should not cause it to be compiled. If your ASDF-LOAD uses :FORCE, that's a the obvious reason, but if not I suspect something funny is going on with timestamps on those files since ASDF feels the need to recompile them. Cheers, -- Nikodemus > The context: I'm writing a wiki (yes, yet another one), and its back-end > consists of plain-text files while I get to grips with writing a parser. > > The text-file wrangling calls on cl-fad, which uses sb-posix, which in > turn makes use of sb-grovel. > Somewhere between 1.0.39 and 1.0.40, a change was made that broke > sb-posix, at least on the two machines I use - both run 64-bit Linux, one > on AMD and one on Intel. > > The symptom: sb-grovel's def-to-lisp fails to compile at line 244, where > it tries to evaluate (compile-file tmp-constants :output-file output-file) > after defining 'tmp-constants in this manner: > (let ((tmp-constants (merge-pathnames #p"constants.lisp-temp" > real-output-file))) > > It seems to come down to where source-files are expected to be, i.e. the > ~/.cache tree, and how they're copied there. The problem can be reproduced > on cue by invoking (asdf:oos 'asdf:load-op :sb-posix). This appears as > (asdf-load :sb-posix) below because I'm a lazy git and defined that > abbreviation in my .sbclrc. > > I've been trying to follow along in the source-code, and the nearest > relevant changes appear to be in contrib/asdf/asdf.lisp, but my thinking > has been addled by a nasty head-cold. Could somebody please give me a > pointer to what I need to look at next? What have I missed? Help! > > > Thanks in advance for any useful tips, > James > > > P.S. For those who'd like to see exactly what happens, a bleeding great > copy-and-paste follows... > > * (asdf-load :sb-posix) > > ; compiling file > "/opt/pkgs/sbcl-1.0.41/lib/sbcl/sb-grovel/def-to-lisp.lisp" (written 15 > AUG 2010 07:51:57 PM): > ; compiling (IN-PACKAGE #:SB-GROVEL) > ; compiling (DEFVAR *DEFAULT-C-STREAM* ...) > ; compiling (DEFUN ESCAPE-FOR-STRING ...) > ; compiling (DEFUN SPLIT-CFLAGS ...) > ; compiling (DEFUN C-ESCAPE ...) > ; compiling (DEFUN AS-C ...) > ; compiling (DEFUN PRINTF ...) > ; compiling (DEFUN C-FOR-ENUM ...) > ; compiling (DEFUN C-FOR-STRUCTURE ...) > ; compiling (DEFUN PRINT-C-SOURCE ...) > ; compiling (DEFUN C-CONSTANTS-EXTRACT ...) > ; compiling (DEFCLASS GROVEL-CONSTANTS-FILE ...) > ; compiling (DEFINE-CONDITION C-COMPILE-FAILED ...) > ; compiling (DEFINE-CONDITION A-DOT-OUT-FAILED ...) > ; compiling (DEFMETHOD PERFORM ...) > > ; > /home/james/.cache/common-lisp/sbcl-1.0.41-linux-x86-64/opt/pkgs/sbcl-1.0.41/lib/sbcl/sb-grovel/ASDF-TMP-def-to-lisp.fasl > written > ; compilation finished in 0:00:00.558 > (/opt/pkgs/sbcl-1.0.41/lib/sbcl/sb-posix/constants.lisp > /home/james/.cache/common-lisp/sbcl-1.0.41-linux-x86-64/opt/pkgs/sbcl-1.0.41/lib/sbcl/sb-posix/constants.fasl > /home/james/.cache/common-lisp/sbcl-1.0.41-linux-x86-64/opt/pkgs/sbcl-1.0.41/lib/sbcl/sb-posix/constants.fasl > /home/james/.cache/common-lisp/sbcl-1.0.41-linux-x86-64/opt/pkgs/sbcl-1.0.41/lib/sbcl/sb-posix/foo.c > /home/james/.cache/common-lisp/sbcl-1.0.41-linux-x86-64/opt/pkgs/sbcl-1.0.41/lib/sbcl/sb-posix/a.out > /home/james/.cache/common-lisp/sbcl-1.0.41-linux-x86-64/opt/pkgs/sbcl-1.0.41/lib/sbcl/sb-posix/constants.lisp-temp) > > debugger invoked on a SB-INT:SIMPLE-FILE-ERROR in thread #<THREAD > "initial > thread" RUNNING > {1002AC20A1}>: > failed to find the TRUENAME of > /home/james/.cache/common-lisp/sbcl-1.0.41-linux-x86-64/opt/pkgs/sbcl-1.0.41/lib/sbcl/sb-posix/constants.lisp-temp: > No such file or directory > > Type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL. > > restarts (invokable by number or by possibly-abbreviated name): > 0: [TRY-RECOMPILING] Try recompiling constants > 1: [RETRY ] Retry performing #<ASDF:COMPILE-OP NIL > {1003B23C31}> on > #<SB-GROVEL:GROVEL-CONSTANTS-FILE > "sb-posix" "constants">. > 2: [ACCEPT ] Continue, treating #<ASDF:COMPILE-OP NIL {1003B23C31}> > on > #<SB-GROVEL:GROVEL-CONSTANTS-FILE > "sb-posix" "constants"> > as having been successful. > 3: [ABORT ] Exit debugger, returning to top level. > > (SB-IMPL::SIMPLE-FILE-PERROR > "failed to find the TRUENAME of ~A" > #P"/home/james/.cache/common-lisp/sbcl-1.0.41-linux-x86-64/opt/pkgs/sbcl-1.0.41/lib/sbcl/sb-posix/constants.lisp-temp" > 2) > 0] backtrace > > 0: (SB-IMPL::SIMPLE-FILE-PERROR > "failed to find the TRUENAME of ~A" > #P"/home/james/.cache/common-lisp/sbcl-1.0.41-linux-x86-64/opt/pkgs/sbcl-1.0.41/lib/sbcl/sb-posix/constants.lisp-temp" > 2) > 1: ((FLET SB-IMPL::FAIL) > "failed to find the TRUENAME of ~A" > #P"/home/james/.cache/common-lisp/sbcl-1.0.41-linux-x86-64/opt/pkgs/sbcl-1.0.41/lib/sbcl/sb-posix/constants.lisp-temp" > 2) > 2: (SB-IMPL::QUERY-FILE-SYSTEM > #P"/home/james/.cache/common-lisp/sbcl-1.0.41-linux-x86-64/opt/pkgs/sbcl-1.0.41/lib/sbcl/sb-posix/constants.lisp-temp" > :TRUENAME > T) > 3: (TRUENAME > #P"/home/james/.cache/common-lisp/sbcl-1.0.41-linux-x86-64/opt/pkgs/sbcl-1.0.41/lib/sbcl/sb-posix/constants.lisp-temp") > 4: ((FLET SB-C::TRY-WITH-TYPE) > #P"/home/james/.cache/common-lisp/sbcl-1.0.41-linux-x86-64/opt/pkgs/sbcl-1.0.41/lib/sbcl/sb-posix/constants.lisp-temp" > "lisp" > T) > 5: (SB-C::VERIFY-SOURCE-FILE > #P"/home/james/.cache/common-lisp/sbcl-1.0.41-linux-x86-64/opt/pkgs/sbcl-1.0.41/lib/sbcl/sb-posix/constants.lisp-temp") > 6: (SB-C::VERIFY-SOURCE-FILE > #P"/home/james/.cache/common-lisp/sbcl-1.0.41-linux-x86-64/opt/pkgs/sbcl-1.0.41/lib/sbcl/sb-posix/constants.lisp-temp")[:EXTERNAL] > 7: (COMPILE-FILE > #P"/home/james/.cache/common-lisp/sbcl-1.0.41-linux-x86-64/opt/pkgs/sbcl-1.0.41/lib/sbcl/sb-posix/constants.lisp-temp")[:EXTERNAL] > 8: ((SB-PCL::FAST-METHOD ASDF:PERFORM > (ASDF:COMPILE-OP SB-GROVEL:GROVEL-CONSTANTS-FILE)) > #<unavailable argument> > #<unavailable argument> > #<ASDF:COMPILE-OP NIL {1003B23C31}> > #<SB-GROVEL:GROVEL-CONSTANTS-FILE "sb-posix" "constants">) > 9: ((LAMBDA > (SB-PCL::.PV. SB-PCL::.NEXT-METHOD-CALL. SB-PCL::.ARG0. > SB-PCL::.ARG1.)) > #<unavailable argument> > #<unavailable argument> > #<ASDF:COMPILE-OP NIL {1003B23C31}> > #<SB-GROVEL:GROVEL-CONSTANTS-FILE "sb-posix" "constants">) > 10: ((SB-PCL::FAST-METHOD ASDF::PERFORM-WITH-RESTARTS > (ASDF:COMPILE-OP ASDF:CL-SOURCE-FILE)) > #<unavailable argument> > #S(SB-PCL::FAST-METHOD-CALL > :FUNCTION #<FUNCTION #> > :PV NIL > :NEXT-METHOD-CALL NIL > :ARG-INFO (2)) > #<ASDF:COMPILE-OP NIL {1003B23C31}> > #<SB-GROVEL:GROVEL-CONSTANTS-FILE "sb-posix" "constants">) > 11: ((LAMBDA ())) > 12: ((FLET SB-THREAD::WITH-RECURSIVE-LOCK-THUNK)) > 13: ((FLET #:WITHOUT-INTERRUPTS-BODY-[CALL-WITH-RECURSIVE-LOCK]324)) > 14: (SB-THREAD::CALL-WITH-RECURSIVE-LOCK > #<CLOSURE (FLET SB-THREAD::WITH-RECURSIVE-LOCK-THUNK) {7FFFF79AB6C9}> > #S(SB-THREAD:MUTEX > :NAME "World Lock" > :%OWNER #<SB-THREAD:THREAD "initial thread" RUNNING {1002AC20A1}> > :STATE 1)) > 15: ((FLET SB-C::WITH-IT)) > 16: ((SB-PCL::FAST-METHOD ASDF:OPERATE (T T)) > #<unavailable argument> > #<unavailable argument> > ASDF:LOAD-OP > :SB-POSIX)[:EXTERNAL] > 17: (SB-INT:SIMPLE-EVAL-IN-LEXENV (ASDF-LOAD :SB-POSIX) #<NULL-LEXENV>) > 18: (INTERACTIVE-EVAL (ASDF-LOAD :SB-POSIX))[:EXTERNAL] > 19: (SB-IMPL::REPL-FUN NIL) > 20: ((LAMBDA ())) > 21: (SB-IMPL::%WITH-REBOUND-IO-SYNTAX #<CLOSURE (LAMBDA #) {1002EBD309}>) > 22: (SB-IMPL::TOPLEVEL-REPL NIL) > 23: (SB-IMPL::TOPLEVEL-INIT) > 24: ((LABELS SB-IMPL::RESTART-LISP)) > > 0] > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by > > Make an app they can't live without > Enter the BlackBerry Developer Challenge > http://p.sf.net/sfu/RIM-dev2dev > _______________________________________________ > Sbcl-help mailing list > Sbcl-help(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/sbcl-help >

3 3

[asdf-devel] create temporary Lisp files in fasl directory
by Robert Brown 06 Aug '10

06 Aug '10

I'm using ASDF to build an open source implementation of Google's protocol buffer data serialization library. The code is here: http://github.com/brown/protobuf I've defined a new component type that allows developers to include protobuf message definition files in their Lisp ASDF files: (defclass protobuf-source-file (cl-source-file) ((relative-proto-pathname ... ) (search-path ... ) (:documentation "A protocol buffer definition file.")) When used like this in a system definition: :components ((:protobuf-source-file "foo")) executing the ASDF:LOAD-OP operation causes the file called foo.proto to be translated into foo.lisp by a C++ program, and then compiled into foo.fasl and loaded. Note that foo.lisp is created in the same directory as the system definition, but I would prefer it to be created in the same directory as foo.fasl, which for me is in a subdirectory of ~/.cache/common-lisp. What's the easiest way to accomplish this? I initially tried overriding INPUT-FILES when applied to CL-SOURCE-FILE instances, but ASDF::PERFORM is defined like this: (defmethod perform ((operation compile-op) (c cl-source-file)) (let ((source-file (component-pathname c)) ... ) ... ) Since it calls COMPONENT-PATHNAME to find Lisp source, it will always look in the system definition directory. bob

3 4

Re: [asdf-devel] Performance hit in TRUENAMIZE
by Juan Jose Garcia-Ripoll 25 Jul '10

25 Jul '10

On Fri, Jul 16, 2010 at 12:54 AM, edgar <edgar-rft(a)web.de> wrote: > I think the main problem here is that some implementations > (notably CLISP) differ between files and directories, so > PROBE-FILE cannnot be used to probe files AND directories. Well, SBCL and ECL do not have that problem, AFAIK. But TRUENAMIZE also seems to be used with files, not directories, from what I could gather during the debugging of ASDF. I would abstract those calls into a function PROBE-FILE-AND-DIRECTORY and use PROBE-FILE internally in this function. The purpose would be clear and sensible implementations might profit from that -- maybe the terrible startup times for ASDF might be decreased this way. Juanjo -- Instituto de Física Fundamental, CSIC c/ Serrano, 113b, Madrid 28006 (Spain) http://juanjose.garciaripoll.googlepages.com

2 4

[asdf-devel] Performance hit in TRUENAMIZE
by Juan Jose Garcia-Ripoll 15 Jul '10

15 Jul '10

Why using TRUENAME + ERROR + HANDLER-CASE instead of PROBE-FILE? I have been tracking a completely unrelated bug in ECL but found that for loading all files ASDF calls TRUENAME with the names of FASLs that do not exist. It finds out that by catching the corresponding error and then tries something else. Throwing and catching errors is costly. Why doing that instead of using PROBE-FILE? Juanjo -- Instituto de Física Fundamental, CSIC c/ Serrano, 113b, Madrid 28006 (Spain) http://juanjose.garciaripoll.googlepages.com

2 2

[asdf-devel] ASDF:LOAD-SYSTEM always recompiles some files
by Benjamin Benninghofen 13 Jul '10

13 Jul '10

Look at the following Symbolics System Definition: ;;;(sct:defsystem :foo ;;; (:default-pathname "scratch/" ;;; :default-module-type :lisp) ;;; ;;; (:module foo ("FOO")) ;;; ;;; (:module bar ("BAR") ;;; (:in-order-to (:compile :load) (:load foo))) ;;; ;;; ) I translated this to ASDF as follows: (ASDF:DEFSYSTEM :FOO :COMPONENTS ((:MODULE FOO :PATHNAME "" :COMPONENTS ((:FILE "foo"))) (:MODULE BAR :PATHNAME "" :COMPONENTS ((:FILE "bar")) :IN-ORDER-TO ((ASDF:COMPILE-OP (ASDF:LOAD-OP FOO)) (ASDF:LOAD-OP (ASDF:LOAD-OP FOO)))))) This is not exactly equivalent, because the semantics of :IN-ORDER-TO is different in Symbolics SCT and ASDF. However I get a very strange behavior of the ASDF System. I write the ASDF:DEFSYSTEM form in a file "scratch/sysdcl.lisp" I compiled the system and then restarted Lisp in order to load the system: CL-USER(2): (load "scratch/sysdcl") ; Loading /home/usr/benni/lisp/scratch/sysdcl.lisp T CL-USER(3): (asdf:find-system :foo) #<ASDF:SYSTEM "foo"> CL-USER(4): (asdf:load-system :foo) ; Fast loading /home/usr/benni/lisp/scratch/foo.fasl ;;; Compiling file /home/usr/benni/lisp/scratch/bar.lisp ;;; Writing fasl file /home/usr/benni/lisp/scratch/ASDF-TMP-bar.fasl ;;; Fasl write complete ; Fast loading /home/usr/benni/lisp/scratch/bar.fasl #<ASDF:LOAD-OP NIL @ #x7292bc42> CL-USER(5): As you see it recompiles one of the files. This happens after each restart of Lisp (Allegro CL 8.1). ASDF:LOAD-SYSTEM each time recompiles "bar.lisp" even if no file is changed. Output Translations were disabled by calling (ASDF:DISABLE-OUTPUT-TRANSLATIONS) -- Benjamin Benninghofen Systemanalytiker EADS Defence & Security Military Air Systems Application Software and Processes - OPEM22 Rechliner Straße 85077 Manching - Germany Telephone: +49 (0) 8459 81 78125 Telephone: +49 (0) 89607 78125 Fax: +49 (0) 8459 81 78105 e-Mail: Benjamin.Benninghofen(a)eads.com EADS Deutschland GmbH Registered Office: Ottobrunn District Court of Munich HRB 107 648 Chairman of the Supervisory Board: Dr. Thomas Enders Managing Directors: Dr. Stefan Zoller (chairman), Michael Hecht NOTICE: This message, together with any attachments, may contain privileged and/or confidential information. If you have received this e-mail in error or are not an intended recipient, you may not use, reproduce, disseminate or distribute it; do not open nor save any attachments, delete it immediately from your system and notify the sender promptly by e- mail that you have done so. Thank you.

2 3

[asdf-devel] ASDF 2.004
by Faré 13 Jul '10

13 Jul '10

I blessed 2.111 as 2.004 and released it all. Several minor bugs have been fixed, and implementation vendors are recommended to upgrade. [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] It is a miracle that curiosity survives formal education. — Albert Einstein

1 0

[asdf-devel] Semantic of ASDF Dependencies
by Benjamin Benninghofen 06 Jul '10

06 Jul '10

Assume we have files "packages" "macros" "classes" "methods" "functions" and we want the following dependencies: 1. In order to compile or load any of the other files the file "packages.fasl" must be loaded. 2. In order to compile or load "methods" the file "classes.fasl" must be loaded. 3. The file "macros" contains macros used in "methods" and "functions" and hence "macros.fasl" must be loaded before any of these 2 files is compiled or loaded. Furthermore when "macros" is changed also "methods" and "functions" have to be recompiled even if they are unchanged. 4. There shall be no more dependencies, i.e. when a file different from "macros" is changed, only this file shall be recompiled. With the Symbolics System Construction Tool (SCT) one would use (:USES-DEFINITIONS-FROM macros) for methods and functions and (:IN-ORDER-TO (:COMPILE :LOAD) (:LOAD packages ...)) for the other dependencies. (asdf:defsystem :test1 :description "Test Dependency Processing" :components ( (:file "packages") (:file "macros" :in-order-to ((asdf:compile-op (asdf:load-op "packages")) (asdf:load-op (asdf:load-op "packages")))) (:file "classes" :in-order-to ((asdf:compile-op (asdf:load-op "packages")) (asdf:load-op (asdf:load-op "packages")))) (:file "methods" :depends-on ("macros") :in-order-to ((asdf:compile-op (asdf:load-op "packages" "classes")) (asdf:load-op (asdf:load-op "packages" "classes")))) (:file "functions" :depends-on ("macros") :in-order-to ((asdf:compile-op (asdf:load-op "packages")) (asdf:load-op (asdf:load-op "packages")))) )) Unfortunately this does not work. All of the ASDF dependencies :DEPENDS-ON and :IN-ORDER-TO seem to behave like the SCT :USES-DEFINITIONS-FROM. For example when "classes" is changed it will recompile "methods" too. Is there anything in ASDF that provides the functionality of the SCT :IN-ORDER-TO ? -- Benjamin Benninghofen Systemanalytiker EADS Defence & Security Military Air Systems Application Software and Processes - OPEM22 Rechliner Straße 85077 Manching - Germany Telephone: +49 (0) 8459 81 78125 Telephone: +49 (0) 89607 78125 Fax: +49 (0) 8459 81 78105 e-Mail: Benjamin.Benninghofen(a)eads.com EADS Deutschland GmbH Registered Office: Ottobrunn District Court of Munich HRB 107 648 Chairman of the Supervisory Board: Dr. Thomas Enders Managing Directors: Dr. Stefan Zoller (chairman), Michael Hecht NOTICE: This message, together with any attachments, may contain privileged and/or confidential information. If you have received this e-mail in error or are not an intended recipient, you may not use, reproduce, disseminate or distribute it; do not open nor save any attachments, delete it immediately from your system and notify the sender promptly by e- mail that you have done so. Thank you.

2 1

[asdf-devel] Is this a bug? or my error?
by Louis A. Turk 01 Jul '10

01 Jul '10

asdf version 2.104 invalid method error for #1=#<STANDARD-METHOD ASDF:OPERATION-DONE-P ASDF::AROUND (ASDF:COMPILE-OP T) {AAE52D1}> method: The method #1# on #<STANDARD-GENERIC-FUNCTION ASDF:OPERATION-DONE-P (5)> has an invalid qualifier. Standard method combination requires all methods to have one of the single qualifiers :AROUND, :BEFORE and :AFTER or to have no qualifier at all. [Condition of type SIMPLE-ERROR] Restarts: 0: [ABORT] Return to SLIME's top level. 1: [TERMINATE-THREAD] Terminate this thread (#<THREAD "repl-thread" RUNNING {B558181}>) Backtrace: 0: (SB-PCL::STANDARD-COMPUTE-EFFECTIVE-METHOD ..) 1: (SB-PCL::GET-SECONDARY-DISPATCH-FUNCTION2 ..) 2: (SB-PCL::GET-SECONDARY-DISPATCH-FUNCTION1 ..) 3: (SB-PCL::CACHE-MISS-VALUES-INTERNAL ..) 4: (SB-PCL::CACHE-MISS-VALUES #<STANDARD-GENERIC-FUNCTION ASDF:OPERATION-DONE-P (5)> (#<ASDF:COMPILE-OP NIL {B87D2B9}> #<ASDF:CL-SOURCE-FILE "iterate" "package">) SB-PCL::ACCESSOR) 5: (SB-PCL::INITIAL-DFUN #<STANDARD-GENERIC-FUNCTION ASDF:OPERATION-DONE-P (5)> (#<ASDF:COMPILE-OP NIL {B87D2B9}> #<ASDF:CL-SOURCE-FILE "iterate" "package">)) 6: ((SB-PCL::FAST-METHOD ASDF::DO-TRAVERSE (ASDF:OPERATION ASDF:COMPONENT T)) ..) 7: ((SB-PCL::FAST-METHOD ASDF::DO-TRAVERSE (ASDF:OPERATION ASDF:COMPONENT T)) ..) 8: (ASDF::DO-ONE-DEP #<ASDF:LOAD-OP NIL {B879DC1}> #<ASDF:SYSTEM "iterate"> #<CLOSURE (FLET ASDF::COLLECT) {B87A76D}> ASDF:COMPILE-OP "iterate" NIL) 9: ((FLET ASDF::DEP) ASDF:COMPILE-OP "iterate" NIL) 10: (ASDF::DO-DEP #<ASDF:LOAD-OP NIL {B879DC1}> #<ASDF:SYSTEM "iterate"> #<CLOSURE (FLET ASDF::COLLECT) {B87A76D}> ASDF:COMPILE-OP ("iterate")) 11: ((SB-PCL::FAST-METHOD ASDF::DO-TRAVERSE (ASDF:OPERATION ASDF:COMPONENT T)) ..) 12: ((SB-PCL::FAST-METHOD ASDF::TRAVERSE (ASDF:OPERATION ASDF:COMPONENT)) #<unavailable argument> #<unavailable argument> #<ASDF:LOAD-OP NIL {B879DC1}> #<ASDF:SYSTEM "iterate">) 13: ((SB-PCL::FAST-METHOD ASDF:OPERATE (T T)) #<unavailable argument> #<unavailable argument> ASDF:LOAD-OP #<ASDF:SYSTEM "iterate">)[:EXTERNAL] 14: (ASDF::MODULE-PROVIDE-ASDF :ITERATE) 15: ((LAMBDA (#:G[REQUIRE]13)) ASDF::MODULE-PROVIDE-ASDF) 16: (SB-IMPL::%MAP-FOR-EFFECT-ARITY-1 #<CLOSURE (LAMBDA #) {B873E1D}> (ASDF::MODULE-PROVIDE-ASDF SB-IMPL::MODULE-PROVIDE-CONTRIB)) 17: (REQUIRE :ITERATE NIL) 18: (SB-INT:SIMPLE-EVAL-IN-LEXENV (REQUIRE :ITERATE) #<NULL-LEXENV>) 19: (SWANK::%EVAL-REGION "(require :iterate)\n") 20: ((LAMBDA ())) 21: (SWANK::TRACK-PACKAGE #<CLOSURE (LAMBDA #) {B873A9D}>) 22: (SWANK::CALL-WITH-BUFFER-SYNTAX NIL #<CLOSURE (LAMBDA #) {B873A85}>) 23: (SWANK::%LISTENER-EVAL "(require :iterate)\n") 24: (SB-INT:SIMPLE-EVAL-IN-LEXENV (SWANK:LISTENER-EVAL "(require :iterate)\n") #<NULL-LEXENV>) 25: (SWANK::EVAL-FOR-EMACS (SWANK:LISTENER-EVAL "(require :iterate)\n") "COMMON-LISP-USER" 8) 26: (SWANK::PROCESS-REQUESTS NIL) 27: ((LAMBDA ())) 28: (SWANK-BACKEND::CALL-WITH-BREAK-HOOK #<FUNCTION SWANK:SWANK-DEBUGGER-HOOK> #<CLOSURE (LAMBDA #) {B740E9D}>) 29: ((FLET SWANK-BACKEND:CALL-WITH-DEBUGGER-HOOK) #<FUNCTION SWANK:SWANK-DEBUGGER-HOOK> #<CLOSURE (LAMBDA #) {B740E9D}>) 30: (SWANK::CALL-WITH-BINDINGS ((*STANDARD-OUTPUT* . #) (*STANDARD-INPUT* . #) (*TRACE-OUTPUT* . #) (*ERROR-OUTPUT* . #) (*DEBUG-IO* . #) (*QUERY-IO* . #) ...) #<CLOSURE (LAMBDA #) {B740EB5}>) 31: (SWANK::CALL-WITH-CONNECTION #<SWANK::CONNECTION {AD5A301}> #<CLOSURE (LAMBDA #) {B740E9D}>) 32: (SWANK::HANDLE-REQUESTS #<SWANK::CONNECTION {AD5A301}> NIL) 33: (SWANK::CALL-WITH-BINDINGS NIL #<CLOSURE (LAMBDA #) {B55B08D}>) 34: ((FLET #:WITHOUT-INTERRUPTS-BODY-[BLOCK351]356)) 35: ((FLET SB-THREAD::WITH-MUTEX-THUNK)) 36: ((FLET #:WITHOUT-INTERRUPTS-BODY-[CALL-WITH-MUTEX]293)) 37: (SB-THREAD::CALL-WITH-MUTEX ..) 38: (SB-THREAD::INITIAL-THREAD-FUNCTION) 39: ("foreign function: #x8066EDB") 40: ("foreign function: #x8052A6D") 41: ("foreign function: #x805DD30") 42: ("foreign function: #xB7FB380E")

3 11