<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">I’m both asking how they should be named, and how to advertise them for programmatic consumption.<div class="">For example, and automatic testing program such as that included in quicklisp, should not try to stand-alone</div><div class="">load systems which are not designed to work stand-alone. We have to work around this by artificially</div><div class="">making all systems “work” in standalone enough to fool quicklisp.</div><div class=""><br class=""></div><div class="">quickref is another tool which tries to publish documentation extracted from packages, but quickref would</div><div class="">like to skip packages which are not part of the public API, such as test case packages which may require</div><div class="">other non-public testing frameworks.</div><div class=""><br class=""></div><div class="">It would be nice if asdf had some declarative way of specifying which systems are intended as entry points.</div><div class="">That would also avoid different people relying on non-standard naming conventions to encode declarative </div><div class="">information.</div><div class=""><br class=""></div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 06 Feb 2019, at 15:36, Robert Goldman <<a href="mailto:rpgoldman@sift.info" class="">rpgoldman@sift.info</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta http-equiv="Content-Type" content="text/xhtml; charset=utf-8" class="">
<div class="">
<div style="font-family:sans-serif" class=""><div style="white-space:normal" class=""><p dir="auto" class="">On 6 Feb 2019, at 2:22, Jim Newton wrote:</p>
<blockquote style="border-left:2px solid #777; color:#777; margin:0 0 5px; padding-left:5px" class=""><p dir="auto" class="">When creating an lisp application I usually have one (or several) what I call top-level asdf systems<br class="">
which advertise the public interface to the application, and I may have several internal systems<br class="">
which are used but not intended for public use.</p><p dir="auto" class="">What is the convention with asdf to distinguish entry-point systems from internal/private<br class="">
systems?</p>
</blockquote><p dir="auto" class="">I generally try to use either Faré's "slashy" systems (like "shop2/common") in my work. When I can, it's even better to use a <code style="background-color:#F7F7F7; border-radius:3px; margin:0; padding:0 0.4em" bgcolor="#F7F7F7" class="">:module</code> which isn't visible at all.</p><p dir="auto" class="">I think what you are really asking is "how should I name a system that the user should never load <em class="">directly</em>?" I don't have a great answer to this question.</p>
</div>
</div>
</div>
</div></blockquote></div><br class=""></div></body></html>