From: Richard Stallman <rms@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: bug-cc-mode@gnu.org, acm@muc.de, alan.mackenzie_jwa@nxp.com,
emacs-devel@gnu.org
Subject: Re: Compilation order. Help with makefiles, please!
Date: Fri, 31 Aug 2007 03:34:55 -0400 [thread overview]
Message-ID: <E1IR11r-00083T-4K@fencepost.gnu.org> (raw)
In-Reply-To: <jwvodgoolj4.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Thu, 30 Aug 2007 15:45:56 -0400)
An "easy" solution is to prefer reading the newer .el files rather than the
older .elc when `requiring' a file during byte-compilation.
To solve this problem, it would have to load the newer .el file even
if the feature is already provided.
That is quite different from `require', and I don't think we should
change `require' to do that. But we could add it as a separate new
feature, perhaps called `compilation-require'.
What do you think about that?
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
next prev parent reply other threads:[~2007-08-31 7:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-29 9:57 Compilation order. Help with makefiles, please! Alan Mackenzie_JWA
2007-08-30 7:15 ` Richard Stallman
2007-08-30 19:45 ` Stefan Monnier
2007-08-31 7:34 ` Richard Stallman [this message]
2007-08-31 8:57 ` Alan Mackenzie_JWA
2007-08-31 14:16 ` Stefan Monnier
2007-09-01 4:06 ` Richard Stallman
2007-10-05 21:54 ` Compilation order. Tentative patch Alan Mackenzie
2007-10-06 5:38 ` Mathias Megyei
2007-10-07 0:31 ` Richard Stallman
[not found] <E1IMYuS-00059J-B8@fencepost.gnu.org>
2007-08-26 9:38 ` Compilation order. Help with makefiles, please! Alan Mackenzie
2007-08-26 10:28 ` Michaël Cadilhac
2007-08-26 10:55 ` Alan Mackenzie
2007-08-26 22:46 ` 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=E1IR11r-00083T-4K@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=acm@muc.de \
--cc=alan.mackenzie_jwa@nxp.com \
--cc=bug-cc-mode@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).