unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Juanma Barranquero'" <lekktu@gmail.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 10:56:40 -0800	[thread overview]
Message-ID: <001801c94b41$b8fb1570$c2b22382@us.oracle.com> (raw)
In-Reply-To: <f7ccd24b0811201042j31e6240ice71413f35bfd119@mail.gmail.com>

> 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.

I don't say anything about where the incompatibility comes from. If forced to
guess, though, I too would suppose that it's from (or mostly from) changes
outside the byte-compiler.

What I do know is that I have code that works if byte-compiled in Emacs 22 or
23, but does not work if the 22-byte-compiled code is used in 23. And I believe
that I have code that does not work if the 23-byte-compiled code is used in 22.

My guess is that changes in the treatment of characters are mostly responsible
for the incompatibilities I see, and those are probably mostly (entirely?)
outside of the byte-compiler code.





  reply	other threads:[~2008-11-20 18:56 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
2008-11-20 18:56           ` Drew Adams [this message]
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='001801c94b41$b8fb1570$c2b22382@us.oracle.com' \
    --to=drew.adams@oracle.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=lekktu@gmail.com \
    --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).