Re: Release of CC Mode 5.31

[storm@cua.dk (Kim F. Storm)]

Stefan Monnier <monnier@iro.umontreal.ca> writes:

>>> 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").

This means that you can work on a .el file for a period of time
without making emacs useless if you happen to exit and restart emacs
in case there are errors in that file.

OTOH, I wish emacs would unconditionally load .el files if started
with -D option so it was easier to debug stuff without having to guess
what code is executed by the byte-compiler.

But then again, it would make debugging of errors in byte-compiler
more difficult...


Anyways, none of this as any effect on lisp code loaded into the
dumped emacs, which is also known to confuse users...

-- 
Kim F. Storm <storm@cua.dk> http://www.cua.dk



-------------------------------------------------------
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