<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=""><div><blockquote type="cite" class=""><div class=""><div style="font-family:sans-serif" class=""><div style="white-space:normal" class=""><br class="">
</div>
<div style="white-space:normal" class=""><blockquote style="border-left:2px solid #777; color:#777; margin:0 0 5px; padding-left:5px" class=""><p dir="auto" class="">I’m both asking how they should be named, and how to advertise them for programmatic consumption.<br class="">
For example, and automatic testing program such as that included in quicklisp, should not try to stand-alone<br class="">
load systems which are not designed to work stand-alone. We have to work around this by artificially<br class="">
making all systems “work” in standalone enough to fool quicklisp.</p>
</blockquote></div>
<div style="white-space:normal" class=""><p dir="auto" class="">Can you explain the quicklisp constraint? How does it find all systems?</p><p dir="auto" class="">One simple expedient for <em class="">this</em> quicklisp issue -- if I understand it correctly -- would be to have a <code style="background-color:#F7F7F7; border-radius:3px; margin:0; padding:0 0.4em" bgcolor="#F7F7F7" class="">test-op</code> default <code style="background-color:#F7F7F7; border-radius:3px; margin:0; padding:0 0.4em" bgcolor="#F7F7F7" class="">perform</code> method for all systems that simply succeeds. It should probably by default issue a warning that no "real" test method exists, and that warning should have a particular type so that it can be muffled by quicklisp. Probably also we should allow the programmer of the original system to make a <code style="background-color:#F7F7F7; border-radius:3px; margin:0; padding:0 0.4em" bgcolor="#F7F7F7" class="">test-op</code> no-op method that emits no warning (because the system is intended not to be testable).</p></div></div></div></blockquote></div><div><br class=""></div><div>As I understand quicklisp, it ties to compile each system in a top-level sbcl, and asserts that that works. </div><div>As far as I know that is the only test it does. I don’t believe it does anything special with test-op.</div><div><br class=""></div><div><br class=""></div><br class=""><div class=""><br class=""></div></body></html>