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:42:10 +0100 [thread overview]
Message-ID: <f7ccd24b0811201042j31e6240ice71413f35bfd119@mail.gmail.com> (raw)
In-Reply-To: <000f01c94b3d$f324c010$c2b22382@us.oracle.com>
On Thu, Nov 20, 2008 at 19:29, Drew Adams <drew.adams@oracle.com> wrote:
> Most, yes, probably. The byte-compiler changes probably affect only a minority
> of code in incompatible ways. But it's enough. ;-)
Hmm. I could be wrong, but I don't remember any changes in the 23.X
byte compiler / interpreter stuff making old (22.X, not 19.X ;-)
byte-code incompatible.
Any such fails is more likely to be from the lisp code than the byte-code.
(Of course 23.X files use a different coding system, so they are not
back-compatible.)
> Agreed. But if the uncompiled code works on two different platforms, then so
> should the byte-compiled code (compiled with the same release #).
"Should" does not imply "must", of course. You can use compile-time
tricks to do almost anything, including generating code which bears no
relation to the original lisp...
Juanma
next prev parent reply other threads:[~2008-11-20 18:42 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
2008-11-20 18:29 ` Drew Adams
2008-11-20 18:42 ` Juanma Barranquero [this message]
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=f7ccd24b0811201042j31e6240ice71413f35bfd119@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).