From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Pterodactyl Gnus v0.39 is released
Date: 26 Oct 1998 01:26:14 +0100 [thread overview]
Message-ID: <m3af2kp3rt.fsf@sparky.gnus.org> (raw)
In-Reply-To: Hrvoje Niksic's message of "26 Oct 1998 00:59:04 +0100"
Hrvoje Niksic <hniksic@srce.hr> writes:
> But these things are not the point. The point is that the crucial
> difference (IMHO) is whether the code is interpreted or compiled, not
> how it is compiled.
I agree totally. And byte-compiled code is interpreted, so the
important distinction here is Lisp/byte-code on the one hand, and
native code on the other. :-)
> I don't buy the notion that a byte-compiled function is somehow
> "less compiled" because it's not compiled to native code.
Well -- it *is* less compiled.
> So, the moment XEmacs developers decided to abstract away a "compiled
> function" object, I believe they chose a good name for the accessor
> functions.
And to me it's a nice example of an abstraction that obscures what the
reality is.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~1998-10-26 0:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-10-25 5:24 Lars Magne Ingebrigtsen
1998-10-25 6:01 ` Shenghuo ZHU
1998-10-25 16:46 ` Lars Magne Ingebrigtsen
1998-10-25 14:24 ` Hrvoje Niksic
1998-10-25 16:49 ` Lars Magne Ingebrigtsen
1998-10-25 19:45 ` Hrvoje Niksic
1998-10-25 22:27 ` Lars Magne Ingebrigtsen
1998-10-25 22:51 ` Hrvoje Niksic
1998-10-25 23:02 ` Lars Magne Ingebrigtsen
1998-10-25 23:59 ` Hrvoje Niksic
1998-10-26 0:26 ` Lars Magne Ingebrigtsen [this message]
1998-10-26 1:17 ` Hrvoje Niksic
1998-10-26 8:07 ` Kai Grossjohann
1998-10-26 13:00 ` Ignored MIME types! Hrvoje Niksic
1998-10-26 15:58 ` Wes Hardaker
1998-10-27 13:14 ` Robert Bihlmeyer
1998-10-26 21:06 ` Lars Magne Ingebrigtsen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3af2kp3rt.fsf@sparky.gnus.org \
--to=larsi@gnus.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 NNTP newsgroup(s).