unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: gnuist006@gmail.com
To: help-gnu-emacs@gnu.org
Subject: How do I get the definition of a function ?
Date: Sat, 20 Oct 2007 20:55:31 -0000	[thread overview]
Message-ID: <1192913731.881996.244460@v29g2000prd.googlegroups.com> (raw)

How do I get the definition, ie source code of a function in emacs
lisp ?

But if it shows some binary or opcode string.

How do I decompile the string ?

Please paste the session of an example
using eval last sexp or eval print last sexp.

Also what is the mathematics of the opcodes ?
Is it related to the combinators in any way ?
Is there any mathematics to speed up the interpretation
of these opcodes and keep their size minimal? Is there
any relation to the mathematics behind the lisp machines?

Just want to see the whole picture.

Thanks a lot for elucidation.

Gnuist

             reply	other threads:[~2007-10-20 20:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-20 20:55 gnuist006 [this message]
2007-10-20 21:42 ` How do I get the definition of a function ? Harald Hanche-Olsen
2007-10-20 23:24 ` Bastien
2007-10-23 14:24 ` Jason

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1192913731.881996.244460@v29g2000prd.googlegroups.com \
    --to=gnuist006@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).