comparison lisp/emacs-lisp/bytecomp.el @ 110705:039bf20a0a30

Add minor comment (Bug#7001).

110704:016990bf37ad

         (setq bytecomp-outbuffer (get-buffer-create " *Compiler Output*"))
       (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.
       (setq overwrite-mode 'overwrite-mode-binary))
     (displaying-byte-compile-warnings
      (with-current-buffer bytecomp-inbuffer
	(and bytecomp-filename
	     (byte-compile-insert-header bytecomp-filename bytecomp-outbuffer))

110705:039bf20a0a30

         (setq bytecomp-outbuffer (get-buffer-create " *Compiler Output*"))
       (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))
     (displaying-byte-compile-warnings
      (with-current-buffer bytecomp-inbuffer
	(and bytecomp-filename
	     (byte-compile-insert-header bytecomp-filename bytecomp-outbuffer))