From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.cc-mode.general,gmane.emacs.devel Subject: Re: Release of CC Mode 5.31 Date: Thu, 08 Dec 2005 17:24:45 -0500 Message-ID: <87bqzrcjth.fsf-monnier+emacs@gnu.org> References: NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1134080746 570 80.91.229.2 (8 Dec 2005 22:25:46 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 8 Dec 2005 22:25:46 +0000 (UTC) Cc: mast@lysator.liu.se, romain@orebokech.com, emacs-devel@gnu.org, bug-cc-mode@gnu.org, henrik.enberg@telia.com, acm@muc.de Original-X-From: cc-mode-help-admin@lists.sourceforge.net Thu Dec 08 23:25:42 2005 Return-path: Original-Received: from lists-outbound.sourceforge.net ([66.35.250.225]) by ciao.gmane.org with esmtp (Exim 4.43) id 1EkUCY-0002jR-9a for sf-cc-mode-help@m.gmane.org; Thu, 08 Dec 2005 23:25:22 +0100 Original-Received: from sc8-sf-list1-b.sourceforge.net (sc8-sf-list1-b.sourceforge.net [10.3.1.7]) by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP id 7772616F64; Thu, 8 Dec 2005 14:25:21 -0800 (PST) Original-Received: from sc8-sf-mx2-b.sourceforge.net ([10.3.1.92] helo=mail.sourceforge.net) by sc8-sf-list1.sourceforge.net with esmtp (Exim 4.30) id 1EkUC5-0005EL-Kj for cc-mode-help@lists.sourceforge.net; Thu, 08 Dec 2005 14:24:53 -0800 Original-Received: from fencepost.gnu.org ([199.232.76.164]) by mail.sourceforge.net with esmtps (TLSv1:DES-CBC3-SHA:168) (Exim 4.44) id 1EkUC3-0001mW-38 for cc-mode-help@lists.sourceforge.net; Thu, 08 Dec 2005 14:24:53 -0800 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by fencepost.gnu.org with esmtp (Exim 4.34) id 1EkUBM-0004jR-2l for bug-cc-mode@gnu.org; Thu, 08 Dec 2005 17:24:08 -0500 Original-Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim 4.34) id 1EkUDO-0003Pn-PV for bug-cc-mode@gnu.org; Thu, 08 Dec 2005 17:26:15 -0500 Original-Received: from [209.226.175.97] (helo=tomts40-srv.bellnexxia.net) by monty-python.gnu.org with esmtp (Exim 4.34) id 1EkUDO-0003PX-Fq; Thu, 08 Dec 2005 17:26:14 -0500 Original-Received: from alfajor ([70.49.81.194]) by tomts40-srv.bellnexxia.net (InterMail vM.5.01.06.13 201-253-122-130-113-20050324) with ESMTP id <20051208222446.TWM5216.tomts40-srv.bellnexxia.net@alfajor>; Thu, 8 Dec 2005 17:24:46 -0500 Original-Received: by alfajor (Postfix, from userid 1000) id E6427D7377; Thu, 8 Dec 2005 17:24:45 -0500 (EST) Original-To: Eli Zaretskii In-Reply-To: (Eli Zaretskii's message of "Thu, 08 Dec 2005 21:47:23 +0200") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux) X-Originating-IP: [0] X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on monty-python X-Spam-Level: X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.63 X-Spam-Score: 1.0 (+) X-Spam-Report: Spam Filtering performed by sourceforge.net. See http://spamassassin.org/tag/ for more details. Report problems to http://sf.net/tracker/?func=add&group_id=1&atid=200001 1.0 X_ORIG_IP_NOT_IPV4 X-Originating-IP doesn't look like IPv4 address Original-Sender: cc-mode-help-admin@lists.sourceforge.net Errors-To: cc-mode-help-admin@lists.sourceforge.net X-BeenThere: cc-mode-help@lists.sourceforge.net X-Mailman-Version: 2.0.9-sf.net Precedence: bulk List-Unsubscribe: , List-Id: Bug reports, feature requests, and general talk about CC Mode. List-Post: List-Help: List-Subscribe: , List-Archive: X-Original-Date: Thu, 08 Dec 2005 17:24:45 -0500 Xref: news.gmane.org gmane.emacs.cc-mode.general:2777 gmane.emacs.devel:47261 Archived-At: >> 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