From ... From: Erik Naggum Subject: Re: inspect Date: 2000/01/13 Message-ID: <3156777199553156@naggum.no>#1/1 X-Deja-AN: 572198632 References: <2hu2kiyuac.fsf@dslab7.cs.uit.no> mail-copies-to: never Content-Type: text/plain; charset=us-ascii X-Complaints-To: newsmaster@eunet.no X-Trace: oslo-nntp.eunet.no 947788829 14680 195.0.192.66 (13 Jan 2000 18:40:29 GMT) Organization: Naggum Software; +47 8800 8879 or +1 510 435 8604; fax: +47 2210 9077; http://www.naggum.no User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.5 Mime-Version: 1.0 NNTP-Posting-Date: 13 Jan 2000 18:40:29 GMT Newsgroups: comp.lang.lisp * Frode Vatvedt Fjeld | Are there functions to access the same information that I can dig up | interactively with INSPECT? usually, but not necessarily. | For example, in ACL, I can (interactively) inspect a compiled function, | and retrieve its machine-code (vector) object through the function's CODE | cell. Is there some function I can use to obtain the same information | programmatically, like | | (get-cell-or-something #'myfun 'code) => # some of these slots are so low-level that there aren't any regular CL-level code to access them. however, the code for the inspector is part of the source code offering that comes with a regular license. it seems that you're digging so deep into Allegro CL that you would benefit from Franz Inc's excellent support, and I think it's fair to pay for a license. I could argue that it's not in the best interest of the continued existence free versions that people reverse-engineer a free product -- it may turn out to be hostile to the commercial operation whose profitability spawned the ability to give something away... however, you should check out the results of (apropos "_CODE"). #:Erik