Remove obsolete use of binary-overwrite-mode in bytecomp (Bug#7001).

* emacs-lisp/bytecomp.el (byte-compile-from-buffer): Remove
obsolete use of binary-overwrite-mode (Bug#7001).

diff --git a/lisp/ChangeLog b/lisp/ChangeLog
index 23be6ed8c287a19079e59e828fd4b74341df5e8a..076c3ef3fac2b1283481215f512471d58059fad7 100644 (file)
--- a/lisp/ChangeLog
+++ b/lisp/ChangeLog
@@ -1,3 +1,8 @@
+2010-10-03  Chong Yidong  <cyd@stupidchicken.com>
+
+       * emacs-lisp/bytecomp.el (byte-compile-from-buffer): Remove
+       obsolete use of binary-overwrite-mode (Bug#7001).
+
 2010-10-03  Glenn Morris  <rgm@gnu.org>
 
        * obsolete/x-menu.el: Remove file, obsolete since 21.1

diff --git a/lisp/emacs-lisp/bytecomp.el b/lisp/emacs-lisp/bytecomp.el
index c0dc1764647125edef12b04048078dedda59f8b2..b3ac7b83d7954ebf3954dd975f6168ebb4f9d4a9 100644 (file)
--- a/lisp/emacs-lisp/bytecomp.el
+++ b/lisp/emacs-lisp/bytecomp.el
@@ -1800,15 +1800,7 @@ With argument ARG, insert value in current buffer after the form."
        (set-buffer-multibyte t)
        (erase-buffer)
        ;;       (emacs-lisp-mode)
-       (setq case-fold-search nil)
-       ;; This is a kludge.  Some operating systems (OS/2, DOS) need
-       ;; to write files containing binary information specially.
-       ;; Under most circumstances, such files will be in binary
-       ;; overwrite mode, so those OS's use that flag to guess how
-       ;; they should write their data.  Advise them that .elc files
-       ;; need to be written carefully.  (There's no point running the
-       ;; mode hook, so don't call `binary-overwrite-mode'.)
-       (setq overwrite-mode 'overwrite-mode-binary))
+       (setq case-fold-search nil))
      (displaying-byte-compile-warnings
       (with-current-buffer bytecomp-inbuffer
        (and bytecomp-filename