Hi,
when I read your post, I instantly came up with the system that may
not be the target of OPERATE like
;; foo.asd
;; https://gist.github.com/privet-kitty/84350b73d528533ac8e19e5bba6aa333
(defpackage :foo.asdf
(:use :cl :asdf :uiop)
(:export #:hideable-system))
(in-package :foo.asdf)
>
> 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
>
On 6 Feb 2019, at 9:02, Jim Newton wrote:
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
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
around this
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 systems
which are used but not intended for public use.
What
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
