From: Richard Stallman <rms@gnu.org>
To: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: dann@ics.uci.edu, monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: byte compiling defcustom
Date: Tue, 20 Nov 2007 07:12:26 -0500 [thread overview]
Message-ID: <E1IuRxq-0004Dh-Lr@fencepost.gnu.org> (raw)
In-Reply-To: <200711192044.lAJKidLh003491@jane.dms.auburn.edu> (message from Luc Teirlinck on Mon, 19 Nov 2007 14:44:39 -0600 (CST))
It seems clear that in terms of actual optimization,any gains would be
neglegible and the main reason to compile would be to emit warnings.
To me, no change seems necessary, but if the lack of warnings worries
people, can the compiler not just warn about, say, obsolete variables
and such without _changing_ anything about the code, leaving this up
to the author or maintainer.
That is an interesting idea.
next prev parent reply other threads:[~2007-11-20 12:12 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-15 4:54 byte compiling defcustom Dan Nicolaescu
2007-11-16 4:28 ` Richard Stallman
2007-11-16 15:25 ` Stefan Monnier
2007-11-17 4:53 ` Richard Stallman
2007-11-18 4:07 ` Stefan Monnier
2007-11-17 4:53 ` Richard Stallman
2007-11-17 5:40 ` Dan Nicolaescu
2007-11-17 16:47 ` Luc Teirlinck
2007-11-17 19:06 ` Dan Nicolaescu
2007-11-17 19:51 ` Luc Teirlinck
2007-11-17 20:05 ` Luc Teirlinck
2007-11-18 13:00 ` Richard Stallman
2007-11-18 18:24 ` disappearing custom menu (was: Re: byte compiling defcustom) Dan Nicolaescu
2007-11-18 18:42 ` Drew Adams
2007-11-18 18:47 ` disappearing custom menu Lennart Borgman (gmail)
2007-11-18 19:20 ` martin rudalics
2007-11-18 19:33 ` Dan Nicolaescu
2007-11-18 19:44 ` martin rudalics
2007-11-18 23:41 ` Dan Nicolaescu
2007-11-19 7:58 ` martin rudalics
2007-11-19 12:25 ` Richard Stallman
2007-11-19 13:08 ` martin rudalics
2007-11-19 15:28 ` Drew Adams
2007-11-18 19:57 ` Drew Adams
2007-11-18 22:23 ` martin rudalics
2007-11-17 19:55 ` byte compiling defcustom Luc Teirlinck
2007-11-17 20:32 ` Luc Teirlinck
2007-11-17 20:41 ` Luc Teirlinck
2007-11-18 4:13 ` Luc Teirlinck
2007-11-18 4:32 ` Stefan Monnier
2007-11-18 5:11 ` Luc Teirlinck
2007-11-18 18:04 ` Dan Nicolaescu
2007-11-18 18:41 ` Luc Teirlinck
2007-11-18 23:29 ` Dan Nicolaescu
2007-11-19 7:55 ` Stefan Monnier
2007-11-19 19:03 ` Richard Stallman
2007-11-19 20:44 ` Luc Teirlinck
2007-11-20 12:12 ` Richard Stallman [this message]
2007-11-19 20:48 ` Luc Teirlinck
2007-11-19 19:03 ` Richard Stallman
2007-11-19 12:25 ` Richard Stallman
2007-11-19 15:48 ` Dan Nicolaescu
2007-11-20 3:59 ` Richard Stallman
2007-11-17 23:31 ` Richard Stallman
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=E1IuRxq-0004Dh-Lr@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=dann@ics.uci.edu \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=teirllm@dms.auburn.edu \
/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).