From: Katsumi Yamaoka <yamaoka@jpl.org>
To: 27340@debbugs.gnu.org
Subject: bug#27340: 26.0.50; byte-compile-delete-errors value changes unexpectedly
Date: Mon, 12 Jun 2017 19:30:43 +0900 [thread overview]
Message-ID: <b4mk24hqyzw.fsf@jpl.org> (raw)
Hi,
When loading a certain Lisp module that requires eieio, the value
of `byte-compile-delete-errors' is changed to t (the default nil)
unexpectedly. For instance:
emacs -batch -Q -l auth-source -eval '(message "%s" byte-compile-delete-errors)'
=> t
Because of this, the byte compiler gets oddly quiet when compiling
a Lisp source on a running Emacs than `batch-byte-compile'. What
changes the value of `byte-compile-delete-errors' is the following
section of eieio-core.el:
--8<---------------cut here---------------start------------->8---
(cl-defstruct (eieio--class
(:constructor nil)
(:constructor eieio--class-make (name))
(:include cl--class)
(:copier nil))
children
initarg-tuples ;; initarg tuples list
(class-slots nil :type eieio--slot)
class-allocation-values ;; class allocated value vector
default-object-cache ;; what a newly created object would look like.
; This will speed up instantiation time as
; only a `copy-sequence' will be needed, instead of
; looping over all the values and setting them from
; the default.
options ;; storage location of tagged class option
; Stored outright without modifications or stripping
)
--8<---------------cut here---------------end--------------->8---
Though I don't know why it changes `byte-compile-delete-errors',
I think it's a bug.
Thanks.
In GNU Emacs 26.0.50 (build 1, i686-pc-cygwin, GTK+ Version 3.18.9)
of 2017-06-12 built on localhost
Windowing system distributor 'The Cygwin/X Project', version 11.0.11900000
next reply other threads:[~2017-06-12 10:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-12 10:30 Katsumi Yamaoka [this message]
2017-06-12 11:12 ` bug#27340: 26.0.50; byte-compile-delete-errors value changes unexpectedly npostavs
2017-06-15 8:49 ` Katsumi Yamaoka
2017-06-16 11:37 ` npostavs
2017-06-19 9:23 ` Katsumi Yamaoka
2017-06-24 14:19 ` npostavs
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=b4mk24hqyzw.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=27340@debbugs.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).