unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: mast@lysator.liu.se, romain@orebokech.com, emacs-devel@gnu.org,
	bug-cc-mode@gnu.org, henrik.enberg@telia.com, acm@muc.de
Subject: Re: Release of CC Mode 5.31
Date: Thu, 08 Dec 2005 17:24:45 -0500	[thread overview]
Message-ID: <87bqzrcjth.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <u1x0nl6b8.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 08 Dec 2005 21:47:23 +0200")

>> When the byte-compiler sees a `require', and the corresponding .elc file is
>> older than the corresponding .el file, it should load the .el file.

> By this very logic, when you (load "foo")---after all, `load' and
> `require' are very similar---Emacs should load foo.el if it is newer
> than foo.elc.

Yes, that too.

> And yet we don't do that, and I think for a very good reason.

I don't know about "very good".  AFAIK the reason is so that you can mess up
the .el file as badly as you want (e.g. with conflict markers when merging
updates) without breaking things and only once you byte-compile will you
make your changes visible to Emacs (kind of like a "commit").

While I don't claim that it's a bad reason, I'm not sure it's that much
better than the reason we're facing which argues to use the other behavior
(prefer the .el over the .elc if the .el is more recent).


        Stefan


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click


  reply	other threads:[~2005-12-08 22:24 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-02 12:20 Release of CC Mode 5.31 Alan Mackenzie
2005-12-02 17:15 ` Henrik Enberg
2005-12-02 20:42   ` Alan Mackenzie
2005-12-03 15:58     ` Richard M. Stallman
2005-12-03 16:15       ` Alan Mackenzie
2005-12-03 11:48   ` Alan Mackenzie
2005-12-03 12:40     ` Romain Francoise
2005-12-03 15:33     ` Henrik Enberg
2005-12-04  3:08     ` Richard M. Stallman
2005-12-05 16:48       ` Alan Mackenzie
2005-12-06 16:43         ` Richard M. Stallman
2005-12-04 19:40     ` Eli Zaretskii
2005-12-04 19:45       ` Romain Francoise
2005-12-06 12:11       ` Alan Mackenzie
2005-12-06 20:33         ` Eli Zaretskii
2005-12-07 17:07           ` Richard M. Stallman
2005-12-07 18:14             ` Alan Mackenzie
2005-12-08  4:53               ` Richard M. Stallman
2005-12-07 18:48             ` Eli Zaretskii
2005-12-07 19:51               ` Stefan Monnier
2005-12-07 22:41                 ` Eli Zaretskii
2005-12-08  4:54                 ` Richard M. Stallman
2005-12-08  4:53               ` Richard M. Stallman
2005-12-08 16:43                 ` Stefan Monnier
2005-12-08 19:47                   ` Eli Zaretskii
2005-12-08 22:24                     ` Stefan Monnier [this message]
2005-12-08 23:04                       ` Kim F. Storm
2005-12-08 23:46                         ` Stefan Monnier
2005-12-09 12:30                           ` Eli Zaretskii
2005-12-09 14:42                             ` Stefan Monnier
2005-12-10  4:13                               ` Richard M. Stallman
2005-12-09 12:35                       ` Eli Zaretskii
2005-12-09 14:42                         ` Stefan Monnier
2005-12-09 15:02                       ` Richard M. Stallman
2005-12-08 23:32                   ` Andreas Schwab
2005-12-09  1:42                   ` Richard M. Stallman
2005-12-08 19:29                 ` Eli Zaretskii
2005-12-09  1:43                   ` Richard M. Stallman
2005-12-06 10:32 ` Romain Francoise
2005-12-06 13:09   ` Alan Mackenzie
2005-12-06 13:46   ` Masatake YAMATO
2005-12-06 20:34   ` Eli Zaretskii
2005-12-06 20:49     ` Romain Francoise
2005-12-06 21:04       ` Eli Zaretskii

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=87bqzrcjth.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=acm@muc.de \
    --cc=bug-cc-mode@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=henrik.enberg@telia.com \
    --cc=mast@lysator.liu.se \
    --cc=romain@orebokech.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).