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

[asdf-devel] always load/compile from sources.
by Pascal J. Bourguignon 16 Mar '12

16 Mar '12

Hi! I have a file swank-stuff.lisp that uses swank if available, with forms such as: #+swank (in-package :swank) #+swank … It contains also definitions that are alway available. If I define it as: (:file "swank-stuff" :depends-on ("other-stuff")) and compile it when I have swank, it produces a .fasl that contains a toplevel (in-pacakge :swank). Therefore when I load the system in an image without swank, it produces this error: ; Loading "com.informatimago.lse.unix-cli" . > Error: There is no package named "SWANK" . > While executing: ccl::set-package, in process listener(1). I tried to define it as: (:file "swank-stuff" :depends-on ("other-stuff") :in-order-to ((asdf:load-op (asdf:compile-op "swank-stuff")))) but it still doesn't work. Is there a way to make it so that swank-stuff is always loaded/compiled from source, instead of from the .fasl file? -- __Pascal Bourguignon__ http://www.informatimago.com/ A bad day in () is better than a good day in {}.

3 5

[asdf-devel] Local package renaming at compile time
by Faré 05 Mar '12

05 Mar '12

It's possible to build CL software with local package renamings using ASDF 2.018 or later, and I have proof: http://common-lisp.net/gitweb?p=users/frideau/package-renaming.git However it (at least currently) requires quite some groundwork if you want to do more than add a non-clashing nickname to an existing package. Below my sigblock is the current relevant section of the README. —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org The naturalistic fallacy: "if it's natural, it's good." The anti-naturalistic fallacy: "if it's natural, it's bad." The a-naturalistic fallacy: "nature has no relationship to good and bad." with-effective-package-renamings and call-with-effective-package-renamings are pretty low-level primitives that let you do what you need, but require you to do a lot of the groundwork. First, an important constraint to understand about building CL software. By intentional design, ASDF only has an :around-compile hook, but no :around-load hook around load, or :around-build hook around both compile and load; indeed, some implementations that rely on linking, such as ECL or GCL, might not even allow any kind of useful hook around loading, and some things one might want to do with fasls (such as linking or concatenating them together into a big fasl) might preclude any such hook. Therefore, whatever renamings you do at compile-time will NOT be done available at load-time. When the fasl is loaded, only the non-renamed names are available, and symbols, stored with the principal name of their package at compile-time, will be resolved against the set of packages at load-time. This imposes this important constraint on renamings that are admissible in ASDF's :around-compile hook: THE (PRINCIPAL) NAME OF A PACKAGE AS RENAMED AT COMPILE-TIME *MUST* BE ONE OF THE NAMES OF THAT PACKAGE AT LOAD-TIME. For instance, if your target package is COM.FOO.BLAH and has nicknames CFBLAH and BLAH, then during your rename, the main name of the package must be one of COM.FOO.BLAH, CFBLAH or BLAH, or the symbols will fail to resolve properly at load-time. You can add as many new local nicknames as you want, and use them locally in your files, you cannot delete all the original names, and you must use the original names in any operation that will happen at runtime or load-time, such as defpackage or find-symbol. Now, if you want to use package-renaming to locally override a package A with another B, it is still possible; but you have to use further tricks. The trick is to somehow ADD a new unique non-clashing nickname to each of the packages that are involved in a clash, at some point after they are defined and before they are used by your code. For instance, give A the nickname A.at.runtime and B the nickname B.at.runtime. Then, you can make B.at.runtime the principal name of whatever renaming you make that targets B, even with local nickname A, whereas A is previously renamed away to A.at.runtime. With this constraint in mind, a typical way to use package-renaming would be to use the following in your my-system.asd file: (defsystem my-system :depends-on (:my-system-meta) :around-compile "my-system-meta::call-with-renamings" ...) And in B-renaming.asd: (defsystem my-system-meta :depends-on (:package-renaming) :components ((:file "renamings"))) And in renamings.lisp: (defpackage :my-system-meta (:use :cl :package-renaming)) (effect-package-renaming '((:A (:A :A.regular.nick :A.at.runtime)) (:B (:B :B.regular.nick :B.at.runtime)))) (defun with-renamings (thunk) (call-with-package-renamings '((:A :A.at.runtime) (:B :B.at.runtime :A :B.other.nick)) thunk)) That's not all that simple, but at least it's possible. If you implement an easier all-in-one solution based on this, I'll happily merge it into this package-renaming.

1 0

[asdf-devel] customize compilation settings for an external system
by Alistair Gee 22 Feb '12

22 Feb '12

My ASDF system depends on some external systems, e.g. clsql-mysql. I want to compile these external systems with particular optimization settings so I have, in my ASD file: ;;; When compiling external systems (and by default), use these optimization settings: (declaim (optimize (compilation-speed 0) (speed 3) (safety 1) (debug 0) (space 0))) (defsystem :my-system :depends-on (:clsql-mysql ...) ... ) Unfortunately, the compilation of clsql-mysql at these optimization settings produces some SBCL optimization notes that I want to muffle. Is it possible to muffle the warnings for just clsql-mysql but not for my-system? I suspect that there is some way to use an :around or :before method to control the compilation of external systems, but I could not figure this out from the ASDF manual. TIA

2 1

[asdf-devel] ELS 2012, Zadar, Croatia
by Marco Antoniotti 01 Feb '12

01 Feb '12

Apologies for the multiple postings. PAPER SUBMISSION DEADLINE EXTENDED European Lisp Symposium 2012, Zadar, Croatia, April 30th - May 1st, 2012 http://european-lisp-symposium.org The purpose of the European Lisp Symposium is to provide a forum for the discussion and dissemination of all aspects of design, implementation and application of any of the Lisp and Lisp-inspired dialects, including Common Lisp, Scheme, Emacs Lisp, AutoLisp, ISLISP, Dylan, Clojure, ACL2, ECMAScript, Racket, SKILL, and so on. We encourage everyone interested in Lisp to participate. The main theme of the 2012 European Lisp Conference is "Interoperability: Systems, Libraries, Workflows". Lisp based and functional-languages based systems have grown a variety of solutions to become more and more integrated with the wider world of Information and Communication Technologies in current use. There are several dimensions to the scope of the solutions proposed, ranging from "embedding" of interpreters in C-based systems, to the development of abstractions levels that facilitate the expression of complex context dependent tasks, to the construction of exchange formats handling libraries, to the construction of theorem-provers for the "Semantic Web". The European Lisp Symposium 2012 solicits the submission of papers with this specific theme in mind, alongside the more traditional tracks which have appeared in the past editions. We invite submissions in the following forms: Papers: Technical papers of up to 15 pages that describe original results or explain known ideas in new and elegant ways. Demonstrations: Abstracts of up to 4 pages for demonstrations of tools, libraries, and applications. Tutorials: Abstracts of up to 4 pages for in-depth presentations about topics of special interest for at least 90 minutes and up to 180 minutes. Lightning talks: Abstracts of up to one page for talks to last for no more than 5 minutes. All submissions should be formatted following the ACM SIGS guidelines and include ACM classification categories and terms. For more information on the submission guidelines and the ACM keywords, see: http://www.acm.org/sigs/publications/proceedings-templates and http://www.acm.org/about/class/1998. Important dates: February 15th 2012: submission deadline (extended deadline) March 7th 2012: acceptance results April 30th 2012: Conference opens Program Commitee. Chair: Marco Antoniotti, Università degli Studi di Milano Bicocca, Milan, ITALY Local organizers: Damir Cavar, Eastern Michigan University Franjo Pehar, University of Zadar Damir Kero, University of Zadar Members: Giuseppe Attardi, Università degli Studi di Pisa, Pisa, ITALY Pascal Costanza, Intel, Bruxelles, BELGIUM Marc Feeley, Université de Montreal, Montreal, CANADA Scott McKay, Google, U.S.A. Kent Pitman, U.S.A. Christophe Rhodes, Department of Computing, Goldsmiths, University of London, London, UNITED KINGDOM Robert Strandh, LABRI, Université de Bordeaux, Bordaux, FRANCE Didier Verna, EPITA / LRDE, FRANCE Taiichi Yuasa, Kyoto University, JAPAN -- Marco Antoniotti

1 0

[asdf-devel] ELS2012 Zadar, Croatia, Call for Papers
by Marco Antoniotti 23 Jan '12

23 Jan '12

Apologies for the multiple postings... =========================================================================== European Lisp Symposium 2012, Zadar, Croatia, April 30th - May 1st, 2012 http://european-lisp-symposium.org The purpose of the European Lisp Symposium is to provide a forum for the discussion and dissemination of all aspects of design, implementation and application of any of the Lisp and Lisp-inspired dialects, including Common Lisp, Scheme, Emacs Lisp, AutoLisp, ISLISP, Dylan, Clojure, ACL2, ECMAScript, Racket, SKILL, and so on. We encourage everyone interested in Lisp to participate. The main theme of the 2012 European Lisp Conference is "Interoperabilty: Systems, Libraries, Workflows". Lisp based and functional-languages based systems have grown a variety of solutions to become more and more integrated with the wider world of Information and Communication Technologies in current use. There are several dimensions to the scope of the solutions proposed, ranging from "embedding" of interpreters in C-based systems, to the development of abstractions levels that facilitate the expression of complex context dependent tasks, to the construction of exchange formats handling libraries, to the construction of theorem-provers for the "Semantic Web". The European Lisp Symposium 2012 solicits the submission of papers with this specific theme in mind, alongside the more traditional tracks which have appeared in the past editions. We invite submissions in the following forms: Papers: Technical papers of up to 15 pages that describe original results or explain known ideas in new and elegant ways. Demonstrations: Abstracts of up to 4 pages for demonstrations of tools, libraries, and applications. Tutorials: Abstracts of up to 4 pages for in-depth presentations about topics of special interest for at least 90 minutes and up to 180 minutes. Lightning talks: Abstracts of up to one page for talks to last for no more than 5 minutes. All submissions should be formatted following the ACM SIGS guidelines and include ACM classification categories and terms. For more information on the submission guidelines and the ACM keywords, see: http://www.acm.org/sigs/publications/proceedings-templates and http://www.acm.org/about/class/1998. Important dates: Jan 31st 2012: submission deadline Feb 21st 2012: acceptance results April 30th, 2012 Conference opens Program Commitee. Chair: Marco Antoniotti, Università degli Studi di Milano Bicocca, Milan, ITALY Local organizers: Damir Ćavar, Eastern Michigan University Franjo Pehar, University of Zadar Damir Kero, University of Zadar Members: Giuseppe Attardi, Università degli Studi di Pisa, Pisa, ITALY Pascal Costanza, Intel, Bruxelles, BELGIUM Marc Feeley, Université de Montreal, Montreal, CANADA Scott McKay, Google, U.S.A. Kent Pitman, U.S.A. Christophe Rhodes, Department of Computing, Goldsmiths, University of London, London, UNITED KINGDOM Robert Strandh, LABRI, Université de Bordeaux, Bordaux, FRANCE Didier Verna, EPITA / LRDE, FRANCE Taiichi Yuasa, Kyoto University, JAPAN -- Marco Antoniotti

1 0

[asdf-devel] Testing for asdf 2.20
by Faré 13 Jan '12

13 Jan '12

There hasn't been much work on ASDF since last month, which is a good sign. I intend to release ASDF 2.20, next week. Can you all test the code we have? NB: I'm removing the intermediate 0 from 2.019, which doesn't mean anything wrt how ASDF interprets version numbers, anyway. Changes since 2.019: * Support the new fasl numbering convention of CCL when generating implementation strings. * Fix a slew of small bug in corner cases of the configuration API, as found by Sergey Katrevich and Rupert Warwick. * Fixed bug in WEAKLY-DEPENDS-ON and added documentation (Robert Goldman). —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org Evil is that which one believes of others. It is a sin to believe evil of others, but it is seldom a mistake. — H.L. Mencken

2 1

[asdf-devel] system reloading behavior
by Yuan Luo 10 Jan '12

10 Jan '12

Hi, I am new to asdf so this might be trivial. When I change a source file and reload the system using (asdf:load-system ...), the compiler re-compiles and re-loads all others source files in that system from scratch, rather than incrementally. Is there some switch to toggle this behavior? Thanks, Yuan

2 1

[asdf-devel] location-function-p.patch
by Сергей Катревич 19 Dec '11

19 Dec '11

Hello! Please review my patch. (and ... (length=n-p x 2) (or ... (and (equal (first x) 'lambda) (cddr x) ;;bug - if (length=n-p x 2) = t, then (cddr x) always = nil (length=n-p (second x) 2))))

2 1

[asdf-devel] Bugfix in split-absolute-pathnames - bad using split-string.
by Сергей Катревич 15 Dec '11

15 Dec '11

Hello! Please apply patch. P.S. This can cause the bug, which is mentioned in "Re: [asdf-devel] XDG_DATA_DIRS and colon separated things"?

2 1

[asdf-devel] oddity in operation-times...
by Robert Goldman 14 Dec '11

14 Dec '11

I think I have found an oddity in ASDF operation times…. If you have a system that doesn't contain any files, then the OPERATION-TIMES never get populated, even if the system is loaded. How can this happen? If you have a system that is loaded simply in order to make a component-dependent-pathname available, then it might not have any files in it. If such a system is loaded, I would expect that the (PERFORM COMPILE-OP SYSTEM) and (PERFORM LOAD-OP SYSTEM) methods should run (well, at least the latter, and that the operation-times for the system should be set. Unfortunately, it seems that if you have an empty system, then the LOAD-OP is never performed on that system object. My guess is that there's some logic that says that you only need to perform an operation on a module if the operation is performed on at least one of its components. I can imagine how we got here, but it seems like a bad fit for this case. <sigh> the semantics of operations on modules never cease to cough up oddities. </sigh> r

1 0