We don't actually. Faré deprecated that. The reasons are complicated,
but basically, it wasn't possible to propagate arguments through a plan.
What do you need an argument for? Maybe there's a work-around.
On 19 Mar 2021, at 16:24, Marco Antoniotti wrote:
BTW.
If you do not advise to
BTW.
If you do not advise to specialize OPERATE, how do you pass arguments to
PERFORM?
MA
On Fri, Mar 19, 2021 at 7:45 PM Robert Goldman wrote:
> P.S. I don't recommend writing your own OPERATE methods -- OPERATE is
> quite complicated and messing with it could lead you into very deep water.
On Fri, 19 Mar 2021, Faré wrote:
On Fri, Mar 19, 2021 at 3:10 AM Andreas Davour wrote:
What more, even Xach […] updated the fallback ASDF in Quicklisp
from 2.26 to 3.2.1!
Didn't he revert that change after something broke?
Not according to the git repository of quicklisp-client.
Also, we
Thanks Robert.
AFAIAC the operation-done-p did the trick. I had skipped it as the doc
says that this operation "may" be provided.
I am not sure how to improve the docs for this task (creating new
operations). I guess a description of what OPERATE and PERFORM actually
invoke and when would
P.S. I don't recommend writing your own `OPERATE` methods -- `OPERATE`
is quite complicated and messing with it could lead you into very deep
water. I don't believe you should ever need to.
On 19 Mar 2021, at 13:42, Robert Goldman wrote:
Hi. I'm happy to help you work through this, but so
Hi. I'm happy to help you work through this, but so that it doesn't
recur as a problem, I'd appreciate it if you would help me fix the
manual's discussion of this.
First, have you read this page
https://common-lisp.net/project/asdf/asdf.html#Creating-new-operations ?
Please have a look at
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
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 OPERATE to actually do something for you.
I know I should
"Robert Goldman" écrivait:
> Didier, would you mind posting a GitLab issue for this? It's feasible,
> but I'm so overloaded right now that there's no chance I will get to
> it before I forget.
Sure!
--
¡En Seguida! -- New album: https://www.didierverna.com/records/en-seguida.php
Available
Didier, would you mind posting a GitLab issue for this? It's feasible,
but I'm so overloaded right now that there's no chance I will get to it
before I forget.
Thanks
On 19 Mar 2021, at 8:34, Didier Verna wrote:
François-René ÐVB Rideau écrivait:
Before it can be ignored, it must be
François-René ÐVB Rideau écrivait:
> Before it can be ignored, it must be defined. And so as to define it,
> its class must be defined. I suppose we could have some error class
> that it used when the class it not defined, that would only trigger an
> error at runtime if the feature is true. I'm
François-René ÐVB Rideau écrivait:
> Using git log test/test-defsystem-depends-on.script it looks like this
> is https://bugs.launchpad.net/asdf/+bug/1445638 Looking for that bug
> in git log, it was fixed in 3.1.4.5 on 2015-04-23.
I'm proceeding with the second issue in my system, and it
On Thu, 18 Mar 2021, Faré wrote:
Considering that SBCL upgraded to 3.1.5 in July 2015, I think you
should be pretty safe assuming that your users' ASDF is more recent
than 3.1.4.
What more, even Xach seems to have miraculously seen the light: one
months and one week ago, he updated the
13 matches
Mail list logo
