From: Eli Zaretskii <eliz@gnu.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: psainty@orcon.net.nz, gazally@runbox.com,
31688-done@debbugs.gnu.org, npostavs@gmail.com,
bug-gnu-emacs-bounces+psainty=orcon.net.nz@gnu.org
Subject: bug#31688: 26.1.50; Byte compiler confuses two string variables
Date: Fri, 08 Jun 2018 18:09:35 +0300 [thread overview]
Message-ID: <834liduxg0.fsf@gnu.org> (raw)
In-Reply-To: <87a7sajxk3.fsf@igel.home> (message from Andreas Schwab on Mon, 04 Jun 2018 19:01:16 +0200)
> From: Andreas Schwab <schwab@linux-m68k.org>
> Date: Mon, 04 Jun 2018 19:01:16 +0200
> Cc: Gemini Lasswell <gazally@runbox.com>, Noam Postavsky <npostavs@gmail.com>,
> bug-gnu-emacs <bug-gnu-emacs-bounces+psainty=orcon.net.nz@gnu.org>,
> 31688@debbugs.gnu.org
>
> On Jun 04 2018, Phil Sainty <psainty@orcon.net.nz> wrote:
>
> > Surely consistent behaviour between compiled and uncompiled code is
> > not only desirable, but a primary goal?
>
> Not if you are using self-modifying code.
Thanks to everyone who participated in the discussion. I have now
added some explanation of these issues to the ELisp manual, and I'm
closing the bug report.
next prev parent reply other threads:[~2018-06-08 15:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-02 17:51 bug#31688: 26.1.50; Byte compiler confuses two string variables Gemini Lasswell
2018-06-02 18:02 ` Noam Postavsky
2018-06-02 22:52 ` Gemini Lasswell
2018-06-02 23:25 ` Noam Postavsky
2018-06-03 0:40 ` Drew Adams
2018-06-02 23:03 ` Drew Adams
2018-06-02 23:38 ` Phil Sainty
2018-06-02 23:54 ` Noam Postavsky
2018-06-03 12:32 ` Phil Sainty
2018-06-03 13:05 ` Andreas Schwab
2018-06-04 10:02 ` Phil Sainty
2018-06-04 15:58 ` Eli Zaretskii
2018-06-04 17:01 ` Andreas Schwab
2018-06-08 15:09 ` Eli Zaretskii [this message]
2018-06-03 0:02 ` Michael Heerdegen
2018-06-03 0:46 ` Drew Adams
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=834liduxg0.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=31688-done@debbugs.gnu.org \
--cc=bug-gnu-emacs-bounces+psainty=orcon.net.nz@gnu.org \
--cc=gazally@runbox.com \
--cc=npostavs@gmail.com \
--cc=psainty@orcon.net.nz \
--cc=schwab@linux-m68k.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.