unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
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: Tue, 19 Jan 2016 20:15:25 +0100	[thread overview]
Message-ID: <87io2pido2.fsf@web.de> (raw)
In-Reply-To: <m28u3lpjk9.fsf@newartisans.com> (John Wiegley's message of "Tue,  19 Jan 2016 09:26:14 -0800")

John Wiegley <jwiegley@gmail.com> writes:

>   3. We then try to print and call the uninterned symbol directly. So what we
>      are calling, and what defun defined, are not the same symbol.

But theoretically, the byte compiler could do it correctly.

This is how the compiled code looks like currently:

(defalias '#1=#:bar #[0 "[bytes...]" [message "function %s called" #1#] 3])
(#:bar)

If the second line would be

(#1#)

(as the compiler already correctly prints in the function body)

the thing would work AFAIU.  I guess it doesn't because it is a
different expression printed separately.

> I recommend closure of this bug as expected behavior,

I think it's quite unexpected, unless you know about how byte
compilation to files works, and even then...

> unless there are further concerns.

I think this is quite a limitation worth to be fixed, if it is possible
with little effort.

If not, we should at least make the compiler raise an error when it
generates function calls like

    (#:bar)

something like that is not very useful, in no situation.


Michael.





  reply	other threads:[~2016-01-19 19:15 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 [this message]
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

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=87io2pido2.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --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).