From ... Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!newsfeed.belnet.be!news.belnet.be!news.tele.dk!small.news.tele.dk!193.213.112.26!newsfeed1.ulv.nextra.no!nextra.com!news01.chello.no!not-for-mail Newsgroups: comp.lang.lisp Subject: Re: Help please: ILisp Hyperspec lookup problem References: <3D12FAD6.C399CC53@smi.de> <3D135E08.E7E16778@smi.de> Mail-Copies-To: never From: Erik Naggum Message-ID: <3233682591958719@naggum.net> Organization: Naggum Software, Oslo, Norway Lines: 22 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 21 Jun 2002 21:09:52 GMT X-Complaints-To: abuse@chello.no X-Trace: news01.chello.no 1024693792 212.186.234.171 (Fri, 21 Jun 2002 23:09:52 MET DST) NNTP-Posting-Date: Fri, 21 Jun 2002 23:09:52 MET DST X-Received-Date: Fri, 21 Jun 2002 23:09:52 MET DST (news01.chello.no) Xref: archiver1.google.com comp.lang.lisp:35411 * Andreas Hinze | Is there a reason why it is separate from ilisp ? Currently it seems to me | that CLHS 6 is supported by Ilisp 5.12 and former CLHS is supported by 5.11 | due to the "hard coded" translation table in hyperspec.el (since i got ilisp | 5.12 around 5 hours ago i have had only a very short look at that file so i | might wrong). It is "hard coded" only because there was no "soft" index when I first wrote this thing. I had to extract the information from some HTML crap and I was not in the mood to do that whenever Emacs needed to build the index. I had no idea Xanalys would go and change the filenames, which seemed rather stupid to me, anyway, but at least they provided a usable index, which was very nice when they first had to go do it. Still, it would be a _lot_ better to have an algorithmic mapping instead of a table lookup, so one could simply use the symbol name. A package could have a base URL as parts of its documentation using the same algorithm to arrive at the actual symbol, the way the function documentation seems to have been designed to help achieve. -- Guide to non-spammers: If you want to send me a business proposal, please be specific and do not put "business proposal" in the Subject header. If it is urgent, do not use the word "urgent". If you need an immediate answer, give me a reason, do not shout "for your immediate attention". Thank you.