From: bojohan+news@dd.chalmers.se (Johan Bockgård)
Subject: Re: goto-line trouble with narrowing
Date: Wed, 01 Feb 2006 08:52:47 +0100 [thread overview]
Message-ID: <yoijbqxrjz1s.fsf@linus003.dd.chalmers.se> (raw)
In-Reply-To: drof87$9gd$1@sea.gmane.org
Kevin Rodgers <ihs_4664@yahoo.com> writes:
> Johan Bockgård wrote:
>> (byte-compile (lambda () (widen))) => #[nil "~\207" [] 1]
>
> Thanks Johan, but you'll have to fill me in on a few details since I
> can't read Emacs Lisp byte code.
No? Try disassemble :)
There is a special byte op-code for `widen' so the compiled function
call doesn't go through the symbol[1].
Compare it with this[2]:
(byte-compile (lambda () (foo))) => #[nil "\300 \207" [foo] 1]
Note the `foo' here and the fact that `widen' isn't mentioned in the
right hand side above.
> Nor do I understand why your example is relevant; isn't this what
> `flet' sets `widen's symbol binding to:
>
> (byte-compile (lambda () t)) => #[nil "\300\207" [t] 1]
Indeed, but the symbol isn't involved.
[1] (disassemble #[nil "~\207" [] 1])
byte code:
args: nil
0 widen
1 return
[2] (disassemble #[nil "\300 \207" [foo] 1])
byte code:
args: nil
0 constant foo
1 call 0
2 return
--
People do not write byte-code; that job is left to the byte compiler.
But we provide a disassembler to satisfy a cat-like curiosity. The
disassembler converts the byte-compiled code into humanly readable
form. -- (info "(elisp)Disassembly")
next prev parent reply other threads:[~2006-02-01 7:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-26 17:01 goto-line trouble with narrowing Robert J. Chassell
2006-01-27 22:32 ` Richard M. Stallman
2006-01-28 19:14 ` Robert J. Chassell
2006-01-30 0:56 ` Richard M. Stallman
2006-01-30 16:57 ` Kevin Rodgers
2006-01-30 18:48 ` Kevin Rodgers
2006-01-30 19:57 ` Johan Bockgård
2006-01-31 19:53 ` Kevin Rodgers
2006-02-01 7:52 ` Johan Bockgård [this message]
2006-01-30 22:31 ` Lennart Borgman
2006-01-31 18:06 ` Richard M. Stallman
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=yoijbqxrjz1s.fsf@linus003.dd.chalmers.se \
--to=bojohan+news@dd.chalmers.se \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).