From: Michael Heerdegen <michael_heerdegen@web.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: chuntaro <chuntaro@sakura-games.jp>, 34757@debbugs.gnu.org
Subject: bug#34757: Invalid bytecode from byte compiler
Date: Fri, 08 Mar 2019 14:50:33 +0100 [thread overview]
Message-ID: <871s3ho4pi.fsf@web.de> (raw)
In-Reply-To: <83k1h9a4ig.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 08 Mar 2019 15:18:31 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> > From: chuntaro <chuntaro@sakura-games.jp>
> > Date: Tue, 5 Mar 2019 17:01:00 +0900
> >
> > Invalid bytecode is output and error occurs when executed.
> >
> > Byte compile the following code.
> >
> > bug.el
> > ----------------------------------------------------------------
> > ;;; -*- lexical-binding: t; -*-
> >
> > (let ((a 2))
> > (print 1)
> > (setq a 1))
> > ----------------------------------------------------------------
> >
> > $ emacs --batch -f batch-byte-compile bug.el
> >
> > bug.elc
> > ----------------------------------------------------------------
> > ;ELC
> > ...
> > ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
> > ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
> >
> >
> > (funcall 2 'print 1)
> > 1
> > ----------------------------------------------------------------
> >
> > $ emacs --batch -l bug.elc
> > Invalid function: 2
>
> Why is that a problem? The Lisp code is invalid, and the error
> message says that much.
Please take a closer look: The Lisp code in the compiled file is
invalid, but the code in the .el isn't.
Michael.
next prev parent reply other threads:[~2019-03-08 13:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-05 8:01 bug#34757: Invalid bytecode from byte compiler chuntaro
2019-03-08 13:18 ` Eli Zaretskii
2019-03-08 13:50 ` Michael Heerdegen [this message]
2019-03-08 14:36 ` Eli Zaretskii
2019-03-08 21:13 ` Pip Cet
2019-03-15 8:08 ` Eli Zaretskii
2019-03-15 14:08 ` Stefan Monnier
2019-03-15 19:40 ` Pip Cet
2019-03-15 20:30 ` Stefan Monnier
2019-03-16 16:51 ` Pip Cet
2019-06-13 11:44 ` Pip Cet
2019-07-27 21:30 ` Stefan Monnier
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=871s3ho4pi.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=34757@debbugs.gnu.org \
--cc=chuntaro@sakura-games.jp \
--cc=eliz@gnu.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 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).