>
> I’m both asking how they should be named, and how to advertise them for
> programmatic consumption.
> For example, and automatic testing program such as that included in
> quicklisp, should not try to stand-alone
> load systems which are not designed to work stand-alone. We have to work
>
ert Goldman wrote:
>
> On 6 Feb 2019, at 2:22, Jim Newton wrote:
>
> When creating an lisp application I usually have one (or several) what I call
> top-level asdf systems
> which advertise the public interface to the application, and I may have
> several internal
When creating an lisp application I usually have one (or several) what I call
top-level asdf systems
which advertise the public interface to the application, and I may have several
internal systems
which are used but not intended for public use.
What is the convention with asdf to distinguish
>
>> For example,what if different hosts want to run the same source code but
>> with different optimization settings?
>> This is a real possibility, as some of my processes are running with
>> profiling (debug 3) and collecting profiling results,
>> and others are running super optimized (speed
Hi Faré,
Thanks for taking the time to understand my comments. I’ve tried to respond to
some
of your questions below. Sorry if my original post wasn’t explicit enough to
give enough
explanation for what I’m trying to do.
If I run several sbcl processes on different nodes in my compute
-file quicklisp-init)
(load quicklisp-init)
(error "file not found ~S" quicklisp-init)))
(asdf:load-system :lisp-types-test)
> On 23 Jan 2018, at 12:47, Pascal Bourguignon <p...@informatimago.com> wrote:
>
>
>
>> On 23 Jan 2018, at 12:
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 same time. What is the best way to
prevent this?
I see in the asdf documentation
Can someone help me with an asdf problem I don’t understand.
When I load quicklisp I get the warning (below) apparently from ASDF.
Advise (b) says that I might: install a newer ASDF and register it in front of
the former in
your configuration,
Can someone explain to me how I can do that?
