asdf-devel December 2018

asdf-devel@common-lisp.net

10 participants
6 discussions

Extracting a UIOP's manual
by Hugo Ishimaru 26 Mar '19

26 Mar '19

Hi all, I have extracted a UIOP's manual from docstrings: https://privet-kitty.github.io/etc/uiop.html It's not perfect in any means as docstring isn't written in a markup langugage, but will be at least a comprehensive reference. The relevant fork of ASDF is in Github: https://github.com/privet-kitty/asdf/tree/uiop-man/uiop/doc The greater part of the generation conforms to that of Alexandria, which depends on SBCL (sb-texinfo). I send this mail as it states > Help wanted extracting working documentation from UIOP's docstrings. in README.md though I might not understand a historical context. Regards Hugo Ishimaru

5 5

Bad system name warning and ASDF
by Robert Goldman 19 Dec '18

19 Dec '18

I have just pushed 3.3.2.12, which will no longer complain about CL-PPCRE.

2 1

clisp testing on linux
by Robert Goldman 18 Dec '18

18 Dec '18

The latest tweak was followed by a Jenkins (linux) test failure for clisp on `test-encodings.script`, with a segmentation fault. I cannot reliably replicate this, and I don't see any reason to assume that this is ASDF's fault, rather than clisp's. I'm not sure that there is anything I can do about this, but thought I would ask for suggestions: ``` Test TEST-FILE-ENCODING-U8: should be UTF-8 ; Registering system test-file-encoding-u8 *** - handle_fault error2 ! address = 0x55f6cc8871d0 not in [0x55db332bd000,0x55db336926d8) ! SIGSEGV cannot be cured. Fault address = 0x55f6cc8871d0. GC count: 203 Space collected by GC: 304757408 Run time: 3 915662 Real time: 4 586182 GC time: 0 693431 Permanently allocated: 165368 bytes. Currently in use: 8753400 bytes. Free space: 1903262 bytes. Segmentation fault (core dumped) Using clisp, test-encodings.script failed ```

2 3

wild-package-inferred-system
by Hugo Ishimaru 18 Dec '18

18 Dec '18

Hi all, I have made an extension of package-inferred-system that interprets star `*' and globstar `**' in a package name, which I will use in the future for my library. https://github.com/privet-kitty/wild-package-inferred-system (My motivation is to eliminate the need for manually creating `foo/.../all'-type subsystems that exist only to use-reexport all .lisp files.) In accordance with the ASDF Best Practices by Faré, I let you know the non-exported facilities of ASDF I had to used: PRIMARY-SYSTEM-P, *DEFPACKAGE-FORMS*, *PACKAGE-INFERRED-SYSTEMS*, AROUND-COMPILE-HOOK, RELATIVE-PATHNAME. I would appreciate any suggestion or correction for the design and implementation of this extension, of course. Regards Hugo Ishimaru

2 1

why does ASDF ask to please only define system/test?
by Mark H. David 14 Dec '18

14 Dec '18

It seems that any system Y associated with a name X must have its name be of the form X/Y. For example, when you build "cl-ppcre", you get this warning: Please only define "cl-ppcre" and secondary systems with a name starting with "cl-ppcre/" (e.g. "cl-ppcre/test") in that file. I've seen this complaint for quite a few systems already. What's the need for this, and is it really worth nagging users of all these systems that have existed in many cases for years and have worked perfectly well without following the new convention? What great functionality are we getting for this? Thanks, -Mark

7 12

Timing compilation
by Didier Verna 05 Dec '18

05 Dec '18

Hello, I would like to collect information about the time it takes to compile an ASDF system (possibly also load it), dependencies excluded. I'm thinking there's probably a way to do this by :around'ing compile-op, or something like that, but if someone already has a clear view on how to make this happen, I'd be grateful for the time spared! Thanks. -- Resistance is futile. You will be jazzimilated. Lisp, Jazz, Aïkido: http://www.didierverna.info

3 7

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

asdf-devel December 2018