From: Kenichi Handa <handa@m17n.org>
To: Dan Nicolaescu <dann@ics.uci.edu>
Cc: emacs-devel@gnu.org
Subject: Re: files in emacs/lisp/language/ not byte compiled
Date: Fri, 04 Jul 2008 11:47:32 +0900 [thread overview]
Message-ID: <E1KEbKe-0001FH-Qz@etlken.m17n.org> (raw)
In-Reply-To: <200807040059.m640xuuC018632@sallyv1.ics.uci.edu> (message from Dan Nicolaescu on Thu, 03 Jul 2008 17:59:56 -0700)
In article <200807040059.m640xuuC018632@sallyv1.ics.uci.edu>, Dan Nicolaescu <dann@ics.uci.edu> writes:
> There are quite a few files in emacs/lisp/language that do not get byte
> compiled (they have a "no-byte-compile: t" local variable setting).
> Is there any particular reason to do that? If not, would you mind if
> that was changed?
They are not compiled because there's no benefit
(memory-space and speed) in doing that.
> The reason to change is that when doing "make recompile" in emacs/lisp
> there are a lot of lines printed about files not being byte compiled.
> This scrolls up legitimate warnings/errors and it is easy to not see them...
If those lines are annoying, I think the right thing is to
find/implement a way to suppress them.
But, frankly speeking, as I don't have a string opinion on
this matter, it's up to Stefan and Yidong.
---
Kenichi Handa
handa@ni.aist.go.jp
next parent reply other threads:[~2008-07-04 2:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200807040059.m640xuuC018632@sallyv1.ics.uci.edu>
2008-07-04 2:47 ` Kenichi Handa [this message]
2008-07-04 4:10 ` files in emacs/lisp/language/ not byte compiled Stefan Monnier
2008-07-04 19:55 ` Glenn Morris
2008-07-04 20:46 ` 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=E1KEbKe-0001FH-Qz@etlken.m17n.org \
--to=handa@m17n.org \
--cc=dann@ics.uci.edu \
--cc=emacs-devel@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).