Re: nnmaildir and XEmacs

[Katsumi Yamaoka <yamaoka@jpl.org>]

>>>>> In <v9slhvff4u.fsf@marauder.physik.uni-ulm.de>
>>>>>	Reiner Steib wrote:
> On Wed, Oct 11 2006, Katsumi Yamaoka wrote:

>> The cause is that `dgnushack-compile' binds the variable `file'.

> dgnushack might be considered harmful.

I think so, but there seems to be no way to solve it except for
improving of Emacs.  Actually Emacs doesn't warn about some
undefined variables.  For instance, the following two forms issue
no warning:

--8<---------------cut here---------------start------------->8---
(byte-compile '(lambda () (list fun macro)))
--8<---------------cut here---------------end--------------->8---
;;
--8<---------------cut here---------------start------------->8---
(progn
  (write-region "\
\(defun foo ()\n\
  (list target-file input-buffer output-buffer))\n"
		nil
		"~/byte-compile-warn-test.el")
  (byte-compile-file "~/byte-compile-warn-test.el"))
--8<---------------cut here---------------end--------------->8---

>> I don't know how XEmacs does it cleverly, though.

XEmacs uses the built-in function `globally-boundp' instead of
`boundp'.

--8<---------------cut here---------------start------------->8---
(let (foo-bar-baz)
  (list (globally-boundp 'foo-bar-baz) (boundp 'foo-bar-baz)))
 => (nil t)
--8<---------------cut here---------------end--------------->8---