asdf-devel November 2017

asdf-devel@common-lisp.net

11 participants
5 discussions

ASDF debugging on Hangouts?
by Faré 27 Dec '17

27 Dec '17

Dear CLers, with ASDF 3.3.1 released and the syntax-control branch pending review, there's not much left for me to do with ASDF before I actually retire. Now I'm looking for hackers to whom to pass the torch of ASDF hacking. It so happens that I seem to have introduced (probably with 3.3.0) a regression that breaks static image dumping of workout-timer with cffi-toolchain. If people are interested, I could do the entire debugging session over Google Hangouts, from isolating the bug and filing a bug report to writing regression test and submitting a merge request. That would be a good way to introduce newcomers to ASDF hacking. Having a public ask questions as I make progress would be a good way to keep the video relevant. Is anyone interested? —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org If there's a book you really want to read but it hasn't been written yet, then you must write it. — Toni Morrison [same with software, —♯f]

8 23

ASDF 3.3.1 is released
by Robert Goldman 17 Nov '17

17 Nov '17

Today we release ASDF 3.3.1, the first bugfix release for the 3.3.0 release series. Of primary interest in this release are 1. a fix for an incompatibility in the UIOP stamp-comparison functions. The handling of infinity as a bound in these functions changed between 3.2 and 3.3, potentially causing problems in backward compatibility. In order to maintain compatibility, the old behavior was restored to the stamp-comparison functions, and new functions -- TIMEstamp comparison functions -- were added to carry the new behaviors. 2. a fix for upgrade from version 3.2.1 3. fixes for bugs that can occur when the default readtable is manipulated inside a dependency loaded by DEFSYSTEM-DEPENDS-ON. We urge implementations that are currently bundling previous versions of ASDF -- and especially those bundling 3.3.0 -- to upgrade to 3.3.1 at their earliest convenience. Here is the changelog entry for 3.3.1: cl-asdf (2:3.3.167-1) unstable; urgency=low New milestone: * UIOP compatibility fix: Introduced new replacement "timestamp" comparison functions, because of inadvertent change in the API. Functions that are compatible with the old semantics are retained as "stamp" comparison functions, but will eventually be deprecated. * Upgrade fix: Upgrade from 3.2.1 needed repair. * Syntax manipulation: Fix for bugs that could be introduced when the default readtable was manipulated during the loading of a defsystem-depends-on system. * Tests: tests for new capabilities and bugs * Documentation: a number of improvements and clarifications.

2 1

RFS: cl-asdf/3.3.1 - Another System Definition Facility
by Kambiz Darabi 15 Nov '17

15 Nov '17

Hello, I have packaged the new upstream release 3.3.1 of the Common Lisp ASDF software and looking for a sponsor: Package name : cl-asdf Version : 2:3.3.1-1 Upstream Author : Robert P. Goldman <rpgoldman(a)sift.info> URL : https://common-lisp.net/project/asdf/ License : Expat Section : lisp The cl-asdf source package builds this binary package: cl-asdf - Another System Definition Facility The package appears to be lintian (2.5.59) clean, apart from: - testsuite-autopkgtest-missing which is in level 'info'. I will try to fix it for the next release after reading the documentation. To access further information about this package, please visit the following URL: http://mentors.debian.net/package/cl-asdf Alternatively, you can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/c/cl-asdf/cl-asdf_3.3.1-1.dsc Changes since the last upload: New upstream release 3.3.1: * UIOP compatibility fix: Introduced new replacement "timestamp" comparison functions, because of inadvertent change in the API. Functions that are compatible with the old semantics are retained as "stamp" comparison functions, but will eventually be deprecated. * Upgrade fix: Upgrade from 3.2.1 needed repair. * Syntax manipulation: Fix for bugs that could be introduced when the default readtable was manipulated during the loading of a defsystem-depends-on system. * Tests: tests for new capabilities and bugs * Documentation: a number of improvements and clarifications. Thank you Kambiz Darabi -- m-creations gmbh Acker 2 55116 Mainz Germany

2 1

Can not upgrade to ASDF 3.3.0
by Vince 06 Nov '17

06 Nov '17

Hello lispers ! I wanted to install the latest ASDF 3.3.0 but got a bunch of errors. I extracted the tar into quicklisp's local-projects and loaded the installation script: (load #p"~/quicklisp/local-projects/asdf/tools/install-asdf.lisp") While evaluating the form starting at line 22, column 0 of #P"/home/vince/quicklisp/local-projects/asdf/tools/load-asdf.lisp": While evaluating the form starting at line 46, column 0 of #P"~/quicklisp/local-projects/asdf/tools/install-asdf.lisp": stacktrace: When attempting to set the slot's value to NIL (SETF of SLOT-VALUE), the slot ASDF/FORCING:FORCED is missing from the object #<ASDF/PLAN:SEQUENTIAL-PLAN {1006E82343}>. [Condition of type SIMPLE-ERROR] Restarts: 0: [RETRY] Retry ASDF operation. 1: [CLEAR-CONFIGURATION-AND-RETRY] Retry ASDF operation after resetting the configuration. 2: [RETRY] Retry EVAL of current toplevel form. 3: [CONTINUE] Ignore error and continue loading file "/home/vince/quicklisp/local-projects/asdf/tools/load-asdf.lisp". 4: [ABORT] Abort loading file "/home/vince/quicklisp/local-projects/asdf/tools/load-asdf.lisp". 5: [RETRY] Retry EVAL of current toplevel form. --more-- Backtrace: 0: ((:METHOD SLOT-MISSING (T T T T)) #<unused argument> #<ASDF/PLAN:SEQUENTIAL-PLAN {1006E82343}> ASDF/FORCING:FORCED SETF NIL) [fast-method] 1: ((LAMBDA (SB-PCL::NEW-VALUE SB-PCL::OBJECT) :IN SB-PCL::SLOT-MISSING-INFO) NIL #<ASDF/PLAN:SEQUENTIAL-PLAN {1006E82343}>) 2: ((:METHOD INITIALIZE-INSTANCE :AFTER (ASDF/PLAN:PLAN-TRAVERSAL)) #<ASDF/PLAN:SEQUENTIAL-PLAN {1006E82343}> :FORCE NIL :FORCE-NOT NIL :SYSTEM NIL) [fast-method] 3: ((SB-PCL::EMF INITIALIZE-INSTANCE) #<unused argument> #<unused argument> #<ASDF/PLAN:SEQUENTIAL-PLAN {1006E82343}> :FORCING #<ASDF/SESSION:FORCING :PERFORMABLE-P T>) 4: ((:METHOD MAKE-INSTANCE (CLASS)) #<STANDARD-CLASS ASDF/PLAN:SEQUENTIAL-PLAN> :FORCING #<ASDF/SESSION:FORCING :PERFORMABLE-P T>) [fast-method] 5: ((LAMBDA NIL :IN ASDF/PLAN:MAKE-PLAN)) 6: ((:METHOD ASDF/OPERATE:OPERATE (ASDF/OPERATION:OPERATION ASDF/COMPONENT:COMPONENT)) #<ASDF/FIND-SYSTEM:DEFINE-OP > #<ASDF/SYSTEM:SYSTEM "asdf"> :PLAN-CLASS NIL :PLAN-OPTIONS NIL) [fast-method] 7: ((SB-PCL::EMF ASDF/OPERATE:OPERATE) #<unused argument> #<unused argument> #<ASDF/FIND-SYSTEM:DEFINE-OP > #<ASDF/SYSTEM:SYSTEM "asdf">) 8: ((LAMBDA NIL :IN ASDF/OPERATE:OPERATE)) 9: ((:METHOD ASDF/OPERATE:OPERATE :AROUND (T T)) #<ASDF/FIND-SYSTEM:DEFINE-OP > #<ASDF/SYSTEM:SYSTEM "asdf">) [fast-method] 10: ((LAMBDA NIL :IN ASDF/SYSTEM:FIND-SYSTEM)) 11: (ASDF/SESSION:CONSULT-ASDF-CACHE (ASDF/SYSTEM:FIND-SYSTEM "asdf") #<CLOSURE (LAMBDA NIL :IN ASDF/SYSTEM:FIND-SYSTEM) {1006E7BB6B}>) 12: ((:METHOD ASDF/COMPONENT:FIND-COMPONENT (STRING T)) "asdf" NIL :REGISTERED NIL) [fast-method] 13: ((:METHOD ASDF/OPERATE:OPERATE (SYMBOL T)) ASDF/LISP-ACTION:LOAD-OP :ASDF :VERBOSE NIL) [fast-method] 14: ((SB-PCL::EMF ASDF/OPERATE:OPERATE) #<unused argument> #<unused argument> ASDF/LISP-ACTION:LOAD-OP :ASDF :VERBOSE NIL) 15: ((LAMBDA NIL :IN ASDF/OPERATE:OPERATE)) 16: ((:METHOD ASDF/OPERATE:OPERATE :AROUND (T T)) ASDF/LISP-ACTION:LOAD-OP :ASDF :VERBOSE NIL) [fast-method] 17: (ASDF/OPERATE:LOAD-SYSTEM :ASDF :VERBOSE NIL) 18: (ASDF/UPGRADE:UPGRADE-ASDF) 19: ((LAMBDA NIL :IN ASDF/OPERATE:OPERATE)) --more-- To Continue a few times does not help. Any hints on that ? I'm on SBCL 1.3.19 and ASDF 3.2.1. Now the reason I want to do this is that it looks like my last solution to build an executable with ECL (I'd like to build a smaller executable than with SBCL). I was hit by the fact that ASDF did not ship make-build, which is the build procedure documented by ECL. Other options like program-op are not really documented either. I explained and keep track of the issue here: https://stackoverflow.com/questions/46520876/building-an-executable-with-ec… :) Regards, Vincent

4 3

Introducing Seed, an interactive software environment built on ASDF
by Andrew Sengul 05 Nov '17

05 Nov '17

Hi everyone, I've created a new software environment based on Common Lisp and it'd be great to get your feedback. Called Seed, this system can be used to create Lisp programs and interact with them in many ways. It's a bit like a web-based IDE, but unlike most IDEs, it uses a visual programming language as its foundation. Seed displays Lisp code in the form of an interactive tree grid. It's possible to create customized interface elements within the tree grid; these elements are converted into Lisp code for compilation. A simple example is a color picker for use choosing colors inside a HTML template. Drop-downs and toggle switches are also easy to insert, and these elements can be composited to create more sophisticated interfaces. And unlike Emacs and other editors that are designed around text files, Seed is designed around editing ASDF systems. When using Seed, the top-level interactive elements are called "systems" - contrast to "buffers" in Emacs. Each Seed system is an ASDF system with particular extensions. Specifically, Seed systems all have a .seed file in their source directory that defines their behavior within the scope of the Seed environment. Check out this video to see Seed in action and a brief tutorial: https://vimeo.com/237947324 This is a slide deck that goes into further detail: https://www.dropbox.com/s/ssjd05bmrfnzg5e/SeedPresentationTechnical.pdf?dl=0 I don't know if Seed is the first general-purpose visual programming environment, but I'm sure its paradigm is among the most flexible. It is implemented as a Web application, with each atom and form within a Lisp program represented by a module manifested using the React framework for JavaScript. Because Seed's interface is implemented in React, the entire ecosystem of React components can be brought to bear when building custom software interfaces. Ready to try Seed out yourself? It's free software and the repo is here: https://github.com/phantomics/seed The installation instructions start here: https://github.com/phantomics/seed#the-first-step-installing-and-running-se… Read the usage tutorial here: https://github.com/phantomics/seed/wiki/Introductory-Tutorial So far, only SBCL has been tested. This is alpha software and you will encounter bugs aplenty. I envision Seed as something that could one day encompass most of the desktop productivity functions that people now use office apps for. The data-driven nature of the interface will make it easy to mash up and modify these tools to design custom workflows.With Lisp's homoiconicity it may even be possible to develop machine learning algorithms to tailor Seed systems to the jobs they're intended to do. Emacs has always been seen as the flagship of Lisp-based environments, but because of its byzantine interface and its tight coupling to the text buffer as the main interactive unit, I can't see a future where Emacs is usable by regular people for desktop productivity. I think Seed may be able to get there. Let me know what you think of Seed, particularly as an ASDF use case. Best, Andrew Sengul

2 6

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

asdf-devel November 2017