Re: Readtable not bound to standard around compilation

Le 22/02/2024 à 05:14, sc...@sympoiesis.com a écrit : Hi all! I just ran into something surprising. This is with ASDF 3.2.1, packaged with Quicklisp. I am using Named-Readtables. I had '*readtable*' set to a nonstandard readtable, then did quickload of a system unrelated to the one that

Re: How to use the current directory?

Le 23/09/2023 à 16:56, Blake McBride a écrit : Thanks for all of the replies!  Although I have been playing with Lisp for many years, I do not have much experience with ASDF or QuickLisp. I appreciate all of the suggestions and explanations, however, with respect, they all seem like

Re: How to use the current directory?

Le 23/09/2023 à 00:04, Blake McBride a écrit : Greetings all! Asdf noob here.  I have spent hours on what I would think would be incredibly simple.  Help would sure be appreciated. I cloned a repo for a package that is available on quicklisp.  I modified it.  However, everytim I do: *

Re: "How-to" request

Le 19/03/2021 à 18:58, Marco Antoniotti a écrit : Hi I am trying to create a new ASDF:OPERATION, but I must be missing something and the manual (or Google) does not seem to help much. How do you create a new operation, which may be quite simple?  Or better, how do you get PERFORM and/or

Re: Question about version in submitting patches

Hi! Le 27/11/2020 à 13:51, Marco Antoniotti a écrit : Hi Sorry for the general noise, not necessarily related to the issue at hand. I know I am a P.I.T.A.,  but I kind of concluded that versions of the kind     MMDD Are better than     major.minor.small.itsy.bitsy.bit What do you

Re: asdf | Can't generate the documentation (#7)

> On 16 May 2019, at 21:16, Hugo Ishimaru wrote: > > Hi. > > Is it enough to begin the Makefile with `all' instead of `website'? > Currently typing `make' leads to the deployment of docs. The first target in a Makefile is the default target. So make the first target the one you want. It

Re: Multiple processing compiling the same file

> On 23 Jan 2018, at 12:00, Jim Newton wrote: > > If I run several sbcl processes on different nodes in my compute cluster, it > might happen that two different runs notice the same file needs to be > recompiled (via asdf), > and they might try to compile it at the

Re: package pollution by asdf

> On 16 Jan 2018, at 17:46, Sam Steingold wrote: > > Hi, > > When I start CLISP with the full linking set (i.e., including all > possible extensions), I have 63 packages in (list-all-packages), and 37 > of them (more than half!) comes from asdf (22 ASDF/* and 15 UIOP/*). > > I

Re: CLISP CLOS style warnings

> On 1 Aug 2017, at 17:21, Pascal Bourguignon <p...@informatimago.com> wrote: > > It works perfectly, but on clisp, since DYNAMICALLY-MODIFIABLE doesn’t come > from EXT. > Where does it come from??? Oh, and but on abcl, which also has a EXT package. I would advise

Re: CLISP CLOS style warnings

> On 1 Aug 2017, at 17:08, Sam Steingold wrote: > >> * Faré [2017-08-01 10:07:33 -0400]: >> >>> To mark a generic function as user-extendable, one can now use a >>> declaration: >>> >>> --8<---cut here---start->8--- >>>

Re: Should marking a system preloaded drop its build information?

Perhaps there could be a asdf operation to load and "freeze" a system? So both options would be available. -- __Pascal Bourguignon__ > Le 15 sept. 2016 à 01:05, Faré a écrit : > > In the patch he submitted, Daniel Kochmanski modified > register-preloaded-system so that it

[asdf-devel] clisp getuid

In asdf.lisp downloaded from the web page this afternoon, line 500. With clisp, the package LINUX is available only in special circumstances. (it has to run on Linux, AND the glibc bindings module must have been compiled AND clisp must have been launched with it, usually with -Kfull). So when