<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On 6 Feb 2013, at 19:01, Hans Hübner wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-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: 0px; font-size: medium; ">I think that some cross-platform mechanism for local nicknames is needed, but I'm not sure whether the hook based package name resolution proposal is really better than an extended defpackage now. It would make sense to have something that implementors would actually (be able to) adopt.</span></blockquote></div><br><div>Once again I'll say it: the advantage of a hook (or some similar substrate mechanism) is that it allows *things other than this specific thing* to be implemented. I regard that as an advantage: perhaps I am alone in that, and everyone else already knows exactly what extra things we would like to be able to happen with package lookup and the complete design is all sorted and done, but I kind of doubt that.</div><div><br></div><div>Is there something preventing CCL adopting a hook? Of the implementations I have looked at (not all in recent history)</div><div>- CMUCL can be hooked</div><div>- SBCL have not looked but probably can</div><div>- LW can be hooked</div><div>- Allegro can be hooked</div><div>- GCL do not know</div><div>- CLISP do not know</div><div>- CCL do not know</div><div><br></div><div><br></div></body></html>