subtle byte-compiler bug

[Oliver Scholz]

David Ponce (CCed here) suggested that this is a bug in the
byte-compiler. He also noted that this bug is not in 21.3.

Please byte-compile the attached file test.el. You'll need a copy of
"wisent-comp.el" which is the grammar compiler from the Wisent parser
generator by David Ponce. You can get the file here:

http://cvs.sourceforge.net/viewcvs.py/*checkout*/cedet/cedet/semantic/wisent/wisent-comp.el?rev=1.19

Then load the byte-compiled file test.elc.

I get this backtrace:

Debugger entered--Lisp error: (void-variable defconst-tmp-var)
  (defconst xpath-tables defconst-tmp-var)
  eval((defconst xpath-tables defconst-tmp-var))
  byte-code( ... )
  load("d:/egoge/akt/lisp/xml/test.elc" nil nil t)
  load-file("~/akt/lisp/xml/test.elc")

I also noticed the following peculiar behaviour:

If I change `(defconst xpath-tables [...]' to `(defvar xpath-tables
[...]' in test.el, I get this backtrace:

Debugger entered--Lisp error: (void-variable defconst-tmp-var)
  (defconst lirum-larum defconst-tmp-var)
  eval((defconst lirum-larum defconst-tmp-var))
                 ^^^^^^^^^^^

Then if I comment the `(defconst lirum-larum [...]' out, so that
there is only the `(defvar xpath-tables [...]', then the file
compiles and loads properly.


Also: adding a docstring to (defconst xpath-tables ...) solves this
problem.

test.el
Description: application/emacs-lisp

    Oliver
-- 
24 Frimaire an 212 de la Révolution
Liberté, Egalité, Fraternité!