From: "Juanma Barranquero" <lekktu@gmail.com>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: Jonathan Groll <lists@groll.co.za>,
GnuEmacs Help <help-gnu-emacs@gnu.org>
Subject: Re: Byte-compiled elisp libraries on different platforms
Date: Thu, 20 Nov 2008 19:08:25 +0100 [thread overview]
Message-ID: <f7ccd24b0811201008o1d455f3ag92113aa4497e3448@mail.gmail.com> (raw)
In-Reply-To: <010201c94b34$281dbd30$c2b22382@us.oracle.com>
On Thu, Nov 20, 2008 at 18:19, Drew Adams <drew.adams@oracle.com> wrote:
> I don't agree about the last part. I have come across things that do not work in
> Emacs 23 if byte-compiled with Emacs 22 (and vice versa).
I was talking only about 22 -> 23, not the other way around.
And of course you can have code that does fail, in subtle or not so
subtle ways. If it does not satisfy the expectations of 23.X
(functions with different parameter profiles, macros whose semantics
has changed, whatever), for example. The only real way to have 100%
compatibility is compiling the .el files with the Emacs release you're
going to use them.
That said, most of the time .elc files generated with 22.X work fine
with 23.X Emacs.
> In general, I believe, Emacs has always been platform-independent wrt
> byte-compiled code,
Yes. But as stated above, whether a .elc file from one Emacs works in
another Emacs is not (just) about byte-code. Of course byte-code must
be compatible, or you're liable to crash Emacs.
Juanma
next prev parent reply other threads:[~2008-11-20 18:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-20 10:47 Byte-compiled elisp libraries on different platforms Jonathan Groll
2008-11-20 11:02 ` Juanma Barranquero
2008-11-20 17:19 ` Drew Adams
2008-11-20 18:08 ` Juanma Barranquero [this message]
2008-11-20 18:29 ` Drew Adams
2008-11-20 18:42 ` Juanma Barranquero
2008-11-20 18:56 ` Drew Adams
2008-11-20 11:02 ` Peter Dyballa
2008-11-22 5:25 ` Xavier Maillard
[not found] <mailman.823.1227178080.26697.help-gnu-emacs@gnu.org>
2008-11-20 10:55 ` Nordlöw
2008-11-21 4:27 ` Tim X
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=f7ccd24b0811201008o1d455f3ag92113aa4497e3448@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=lists@groll.co.za \
/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).