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

[asdf-devel] asdf 2.23, and contribs
by Faré 05 Jul '12

05 Jul '12

Dear fellow lispers, I'd like to release asdf 2.23 around July 14 or so. Can you review the changes so far and test it for stability? Changes since 2.22: * exported more pathname-related utilities from the package asdf * tweak compile-file* to accept a :compile-check argument, and the :around-compile protocol to allow passing flags to compile-file* This allows for a race-condition-free way of imposing strictures on files that are being compiled, and is used by asdf-finalizers. Speaking of which, some time ago, I started to collect asdf extensions, and I just added a listing of them on the asdf webpage. Please suggest more extensions that I may list on the page. Currently listed are: * asdf-contrib, an umbrella that just depends-on other extensions. * asdf-encodings (depends on asdf 2.21), to compile Lisp source files with character encodings other than UTF-8. * asdf-bundle, to bundle one or more systems into a single FASL file, for easier delivery (only on SBCL, CCL and hopefully still ECL, for now). * asdf-condition-control (distributed as part of XCVB), to control which conditions to warn about or to muffle during compilation. * asdf-finalizers, to allow macros, reader-macros or types to include code to be evaluated at the toplevel, at the end of a file being compiled. (I personally think it's very cool.) * asdf-dependency-grovel, to compute the actual dependencies in a big ASDF system (not included by asdf-contrib). * poiu, to compile a system in parallel (not included by asdf-contrib). I suppose I should list CFFI and IOlib (and possibly SB-GROVEL?), maybe cl-protobufs, xcvb-bridge and more, for notably possessing non-trivial ASDF extensions. Or should I? What other systems should I list? —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org Necessity is the plea for every infringement of human freedom. It is the argument of tyrants; it is the creed of slaves. — William Pitt, 1783

2 1

[asdf-devel] asdf 2.22 released
by Faré 16 Jun '12

16 Jun '12

I am pleased to announce the release of ASDF 2.22. Since previous release 2.21, the changes are as follow: * require is now mapped to the recently defined require-system, not to load-system anymore. * more sensible inheritance semantics for default-component-class, which can be either a class or a class name. (hat tip to Nikodemus) * accept wildcards in directory-files for physical pathnames. (hat tip to Erik Pearson). These changes are few and subtle, but nonetheless significant to those who'd use these features. As usual, developers, please test and enjoy, vendors, please update your implementation or distribution. —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org Of course, Third World leaders love you. By ascribing third world ills to First World sins, you absolve them of blame for their countries' failure to advance. — John McCarthy

2 3

[asdf-devel] asfd:implementation-identifier is public on SBCL but private in CLISP
by Anton Vodonosov 03 Jun '12

03 Jun '12

Hello. On SBCL I can access asff:implentation-identifier, but on CLISP i can't. Only asff::implentation-identifier works. Is it OK? ASDF 2.014.6. Best regards, - Anton

2 3

[asdf-devel] toward asdf 2.22
by Faré 03 Jun '12

03 Jun '12

Is anyone working on asdf or desiring a fix to any known bug? Otherwise, I'd like to promote current asdf HEAD (2.21.5) as a release candidate, that Erik Pearson and Nikodemus Siivola might enjoy the improvements done for them. Changes: * require is now mapped to the recently defined require-system, not to load-system anymore. * more sensible inheritance semantics for default-component-class, which can be either a class or a class name. * accept wildcards in directory-files for physical pathnames. —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org Give up all hope for a better yesterday, even a better just now. Never give up hope for a better tomorrow. — Patri Friedman

1 0

[asdf-devel] Various issues
by Tobias C Rittweiler 24 May '12

24 May '12

Hi there! Thanks to the ASDF maintainers. I just visited ASDF's website on common-lisp.net since a long time, and it makes a nicely maintained impression! Well done. I have the following issues: * The rather old ASDF version that I'm using ("2.010") does not seem to be able to cope with multiple :depends-on clauses. (Only one clause seems to be used.) Is this intended behaviour? Might it be fixed in more recent versions? * :STATIC-FILE (and :FILE for that matter) are not discussed or explained in the manual. * We generate a 'version.lisp' with a (DEFPARAMETER ...) form in it when using "make" to build a Lisp binary using buildapp. Is there a component that loads a file if it exists and if it does not exist just skips the clause? Thanks, T

4 5

[asdf-devel] asdf-bundle
by Faré 18 May '12

18 May '12

asdf-bundle is now working (hopefully) on SBCL and CCL as well as ECL, by concatenating fasls. It won't work for systems where CFFI creates .so. Try it! (require :asdf) (require :asdf-bundle) (asdf:oos 'asdf::load-fasl-op :your-favorite-system) It creates a your-favorite-system.system.fasl in the fasl cache. Actually, I'm not sure about ECL anymore - load-fasl-op fails at the last minute (after the fasl-op itself) because it tries doing something with a .fasb even though I didn't enable the bytecode compiler. Since I leveraged that part of the code from asdf's asdf-ecl.lisp, I suspect it is broken there already. Juanjo: can you give a look when you have time? Others: you're welcome to contribute support for your favorite implementations. —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org Don't have good ideas if you aren't willing to be responsible for them. — Alan Perlis

2 1

[asdf-devel] Tests on Mac OS X
by Robert Goldman 17 May '12

17 May '12

I tested on the following lisps ccl clisp sbcl ecl abcl allegro allegromodern with success. Haven't tried on CMUCL yet, because of prior problems. I will see about picking up a snapshot sometime.

1 0

[asdf-devel] lisp source debugger
by Yuan Luo 13 May '12

13 May '12

Hi, This maybe an irrelevant question, if so, please point me to the best list to ask. But I am wondering whether you guys can recommend some source level debugger that can POINT ME PRECISELY to where the error was. For example, Allegro CL cannot because many times it tells me that there is an error in a function, but it doesn't tell me which line even if I set their debug flag to 3 the highest level and suppressed everything else, speed, optimization etc. (my function has hundreds of lines then I am frustrated ...) Best, Yuan

3 2

[asdf-devel] :default-component-class and custom module classes
by Nikodemus Siivola 07 May '12

07 May '12

I was trying to make a custom module class, which would have provided its own :DEFAULT-COMPONENT-CLASS via :DEFAULT-INITARGS, but (setf (module-default-component-class ret) (or default-component-class (and (typep parent 'module) (module-default-component-class parent)))) means that does work as I hoped it would. The closest I can get is by overriding ASDF::MODULE-DEFAULT-COMPONENT-CLASS method, but that seems fairly icky. Is there a better way? Cheers, -- Nikodemus

2 1

[asdf-devel] Reloading a .asd
by Stelian Ionescu 07 May '12

07 May '12

I'm using the elisp snippet below(courtesy of Stas Boukarev with some modifications) to reload a .asd file. Is asdf::load-sysdef the best way to trigger a reload(but not recompilation) ? Use case: I want to work on a system that isn't in the ASDF path, it being one of the many development trees I have around(e.g. CFFI), so I want to be able to say that "this cffi.asd is the CFFI to use during this session". Any ideas ? (defvar slime-custom-file-loaders '(("asd" . slime-load-asdf) ("lisp" . slime-load-file))) (defun slime-load-asdf (filename) (slime-eval-with-transcript `(asdf::load-sysdef ,(file-name-sans-extension filename) ,(slime-to-lisp-filename (expand-file-name filename))))) (defun slime-custom-load-file () (interactive) (unless buffer-file-name (error "Buffer %s is not associated with a file." (buffer-name))) (check-parens) (when (and (buffer-modified-p) (y-or-n-p (format "Save file %s? " (buffer-file-name)))) (save-buffer)) (let* ((type (file-name-extension buffer-file-name)) (loader (cdr (assoc-string type slime-custom-file-loaders t)))) (funcall (or loader 'slime-load-file) buffer-file-name))) (define-key slime-mode-map (kbd "C-c C-l") 'slime-custom-load-file) -- Stelian Ionescu a.k.a. fe[nl]ix Quidquid latine dictum sit, altum videtur. http://common-lisp.net/project/iolib

3 8