unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: John Wiegley <jwiegley@gmail.com>
Cc: Alan Mackenzie <acm@muc.de>, Marcin Borkowski <mbork@amu.edu.pl>,
	John Wiegley <johnw@gnu.org>,
	Helmut Eller <eller.helmut@gmail.com>,
	4845@debbugs.gnu.org
Subject: bug#4845: 23.1.50; Uninterned symbols in .elc files
Date: Wed, 18 Nov 2020 18:41:38 -0800	[thread overview]
Message-ID: <CADwFkmnajB_A0hNOR=26d+0DCUt_tcnL6h84S_wzd+XHXXQs4g@mail.gmail.com> (raw)
In-Reply-To: <m24me9iati.fsf@newartisans.com> (John Wiegley's message of "Tue,  19 Jan 2016 12:16:57 -0800")

tags wontfix
close 4845
thanks

John Wiegley <jwiegley@gmail.com> writes:

>>>>>> Helmut Eller <eller.helmut@gmail.com> writes:
>
>> Interpreted and compiled code behave differently. That's always a problem.
>> Obviously not a big problem.
>
> The number of ways to coax varying behavior from the two execution modes is
> legion. I had to bend over backwards to achieve consistency for use-package
> when byte-compiling an init.el file versus loading it un-byte-compiled. So I
> don't feel this bug is very urgent.
>
>>>>>> Michael Heerdegen <michael_heerdegen@web.de> writes:
>
>> I think this is quite a limitation worth to be fixed, if it is possible with
>> little effort.
>
> Honestly, we have better things to do. If you still think this is a bug, I'm
> fine leaving it open until the day when someone wants to champion the cause of
> interpreted/compiled equivalence, but until then, I'd rather focus on other
> things.

I tend to agree with John here; it doesn't seem worth spending time on
this.  There also have been no further interest in this bug report
within 4 years.

I'm therefore closing this bug report as wontfix.  If anyone disagrees
with that, feel free to reopen.





      reply	other threads:[~2020-11-19  2:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-01  8:25 bug#4845: 23.1.50; Uninterned symbols in .elc files Helmut Eller
2016-01-17 21:12 ` Marcin Borkowski
     [not found] ` <mailman.2481.1453074610.843.bug-gnu-emacs@gnu.org>
2016-01-19 12:39   ` Alan Mackenzie
2016-01-19 17:26     ` John Wiegley
2016-01-19 19:15       ` Michael Heerdegen
2016-02-20  6:23         ` John Wiegley
2016-02-20 10:01         ` Andreas Schwab
2016-01-19 19:44       ` Helmut Eller
2016-01-19 20:16         ` John Wiegley
2020-11-19  2:41           ` Stefan Kangas [this message]

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='CADwFkmnajB_A0hNOR=26d+0DCUt_tcnL6h84S_wzd+XHXXQs4g@mail.gmail.com' \
    --to=stefan@marxist.se \
    --cc=4845@debbugs.gnu.org \
    --cc=acm@muc.de \
    --cc=eller.helmut@gmail.com \
    --cc=johnw@gnu.org \
    --cc=jwiegley@gmail.com \
    --cc=mbork@amu.edu.pl \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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