From: Eli Zaretskii <eliz@gnu.org>
To: chuntaro <chuntaro@sakura-games.jp>
Cc: 34757@debbugs.gnu.org
Subject: bug#34757: Invalid bytecode from byte compiler
Date: Fri, 08 Mar 2019 15:18:31 +0200 [thread overview]
Message-ID: <83k1h9a4ig.fsf@gnu.org> (raw)
In-Reply-To: <ea07c24c-c0da-e7a3-d3d3-6680c664580f@sakura-games.jp> (message from chuntaro on Tue, 5 Mar 2019 17:01:00 +0900)
> 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.
next prev parent reply other threads:[~2019-03-08 13:18 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 [this message]
2019-03-08 13:50 ` Michael Heerdegen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83k1h9a4ig.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=34757@debbugs.gnu.org \
--cc=chuntaro@sakura-games.jp \
/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.