<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "> <br><div><div>On Mar 22, 2009, at 5:52 PM, David Yrueta wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: 'Lucida Grande'; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0; ">I considered this design possibility earlier because it seems to work, but I'd be shocked if it was right. It violates too many of conditions of the design recipe by 1) including a possible value for a-lolon that doesn't exist in it's data definition, and, 2) not using merge-all-neighbors to recur on (merge (first a-lolon) (first (rest a-lolon))). </span></blockquote></div><br><div>But why should it? It's mostly what you want. You're missing a clause, and one additional well-chosen test should reveal this. </div></body></html>