Path: utzoo!attcan!uunet!husc6!mailrus!cornell!uw-beaver!fluke!ssc-vax!bcsaic!rwojcik
From: rwojcik@bcsaic.UUCP (Rick Wojcik)
Newsgroups: comp.lang.lisp
Subject: Re: Another Lucid Question
Message-ID: <6882@bcsaic.UUCP>
Date: 5 Aug 88 00:25:48 GMT
References: <3384@phoenix.Princeton.EDU>
Reply-To: rwojcik@bcsaic.UUCP (Rick Wojcik)
Distribution: na
Organization: Boeing Computer Services AI Center, Seattle
Lines: 24

In article <3384@phoenix.Princeton.EDU> eliot@phoenix.Princeton.EDU (Eliot Handelman) writes:
>My next question is this: how can I access the definition of an
>interpreted function? In KCl #'foo results in (lambda-block foo ...)
>which I can then treat as a list. But in Lucid I get #<intrepreted-function
>FOO ... (and then its address)>, which can't be treated as a list. How do
>I make the sharp-sign go away? I don't want it, and I don't see what it's
>supposed to be doing except cluttering up the definition and preventing
>it from being pretty-printed.
>
Try (grindef <function>).  It's a macro, so you don't have to quote the
function name.  Two of us just wasted about half an hour trying to track
this information down earlier today.  You would think that it would be
referenced in the manual's index under 'function' somewhere.  But Nooooo!!  
That would be too easy.  The method we used to track down this information
was to chance upon a colleague who happened to remember it.  The manual
only tells you about functions that retrieve the useless #<interpreted-function
form. We have found that Lucid's documentation is most useful when you
already know the information that you are trying to look up. ;-) 

-- 
Rick Wojcik   csnet:  rwojcik@boeing.com	   
              uucp:   uw-beaver!ssc-vax!bcsaic!rwojcik 
address:  P.O. Box 24346, MS 7L-64, Seattle, WA 98124-0346
phone:    206-865-3844