<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
<br><div><div>On 2010-03-18, at 00:03 , Juan Jose Garcia-Ripoll wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div class="gmail_quote">On Wed, Mar 17, 2010 at 11:54 PM, Juan Jose Garcia-Ripoll <span dir="ltr"><<a href="mailto:juanjose.garciaripoll@googlemail.com">juanjose.garciaripoll@googlemail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> <div class="gmail_quote"><div class="im">Oh, there is nothing with TRAVERSE's output _right now_.</div></div></blockquote></div><div><br></div><div>Let me clarify this again:</div><div><br></div><div>- The fact that TRAVERSE now adds the same operation for all components was new. That was my source of confusion. Before this did not happen with LIB-OP and the like. Maybe a straightforrwad solution is just writing</div> <div><br></div><div> (defun perform ((o bundle-op) (c component)) nil)</div><div><br></div><div>so that all components which are not modules get a default PERFORM that does nothing. Is this safe?</div></blockquote><div><br></div>if the library adopts an ansi-11.1.2.1.2-like restriction on extensions, this would be compatible, because one of the specializers is not a standard class.</div><div><br></div></body></html>