From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: "Johan Bockgård" <bojohan@gnu.org>
Cc: Noam Postavsky <npostavs@gmail.com>,
Emacs developers <emacs-devel@gnu.org>
Subject: Re: [Emacs-diffs] master c75eb10: Don't change byte-compile-delete-errors at runtime (Bug#27340)
Date: Thu, 29 Jun 2017 16:49:44 -0400 [thread overview]
Message-ID: <jwv1sq2frod.fsf-monnier+emacsdiffs@gnu.org> (raw)
In-Reply-To: <871sq28sk0.fsf@gnu.org> ("Johan Bockgård"'s message of "Thu, 29 Jun 2017 22:09:19 +0200")
> The Hyperspec says that:
>
> 1. [declaim should] make definitions available both in the compilation
> and run-time environments.
Hmm... the uses of declaim that I'm familiar with are optimization
settings for the compiler. These don't "make definitions available"
AFAICT. If foo.el contains a declaim to set the optimization level,
I don't see why it would make sense for this setting to affect all files
compiled after foo.elc was loaded (I can understand that the spec may
allow such a suboptimal behavior, but not that it would require it).
Stefan
next prev parent reply other threads:[~2017-06-29 20:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170624141528.514.4459@vcs0.savannah.gnu.org>
[not found] ` <20170624141530.443C5210EB@vcs0.savannah.gnu.org>
2017-06-24 14:26 ` [Emacs-diffs] master c75eb10: Don't change byte-compile-delete-errors at runtime (Bug#27340) Stefan Monnier
2017-06-24 14:36 ` Noam Postavsky
2017-06-25 19:34 ` Stefan Monnier
2017-06-29 2:04 ` Noam Postavsky
2017-06-29 11:46 ` Stefan Monnier
2017-06-29 19:25 ` Johan Bockgård
2017-06-29 19:46 ` Noam Postavsky
2017-06-29 20:09 ` Johan Bockgård
2017-06-29 20:49 ` Stefan Monnier [this message]
2017-06-29 22:11 ` Johan Bockgård
2017-06-30 6:06 ` Stefan Monnier
2017-07-01 8:59 ` Johan Bockgård
2017-07-01 14:35 ` Stefan Monnier
2017-06-29 20:52 ` 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=jwv1sq2frod.fsf-monnier+emacsdiffs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=bojohan@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=npostavs@gmail.com \
/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).