Re: Prickliness of the "invalid byte code" stuff

[Stefan Monnier <monnier@iro.umontreal.ca>]

> I just did a very simple test: I deleted all the .elc files and then
> said `C-x v g' on a file and got the familiar "invalid byte code"
> message.  At least in this instance it would be more helpful to say that
> the .elc file no longer exists...  or perhaps not backtrace at all, but
> just load .el file?

IIRC while some details can be improved, it's pretty hard to make it
work really well in all cases without making non-trivial changes.

But there's an easy fix for the specific problem you mention (see
attached).

Maybe this fix should be applied to all the relevant files.
[ The lack of smileys is because I'm suggesting this quite seriously:
  AFAIK this is a micro-optimization which doesn't make much sense
  nowadays anyway.  Has anyone bothered to actually measure the speed
  up it can offer?  ]


        Stefan


diff --git a/lisp/emacs-lisp/cl-macs.el b/lisp/emacs-lisp/cl-macs.el
index 24e79acfa5..7e11dd2e4a 100644
--- a/lisp/emacs-lisp/cl-macs.el
+++ b/lisp/emacs-lisp/cl-macs.el
@@ -3397,7 +3397,6 @@ cl-struct-slot-value
 (run-hooks 'cl-macs-load-hook)
 
 ;; Local variables:
-;; byte-compile-dynamic: t
 ;; generated-autoload-file: "cl-loaddefs.el"
 ;; End: