Comparison between integer and character is constant nil (-1 and ?0)

Comparison between integer and character is constant nil (-1 and ?0)

[Francisco Solsona]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii, Size: 1144 bytes --]

	Hello,

	Every time I select a new article I get on the console the
message on the subject line, together with an stack trace:

Comparison between integer and character is constant nil (-1 and ?0)
   [parse-time-tokenize, parse-time-string, byte-code, date-to-time, article-make-date-line, article-date-ut, article-date-lapsed, apply, if, save-excursion, gnus-article-date-lapsed, run-hooks, apply, gnus-run-hooks, gnus-article-prepare-display, gnus-article-prepare, gnus-summary-display-article, <compiled-function of unknown origin>, call-interactively]

	It starts happening when I switch from pgnus-0.66 to
pgnus-0.69, and from Xemacs 20.4 to 21.2 "Artemis" XEmacs Lucid
(beta8). Currently I'm using Pterodactyl Gnus v0.70¹ and the prob
remains. 

	I guess this is due to a change in the way eq behaves in
Xemacs 21.2, but I'm not sure, though. Have you seen this before? I
don't have other (X)Emacs versions around to test.

Notes:
¹ I byte-compiled 0.71, but right now I don't have time to remove
gnus-article-display-hook from .gnus, so I'm still running the *old*
0.70. :-( 

Francisco
-- 
And now for something completely different.

Re: Comparison between integer and character is constant nil (-1 and ?0)

[Hrvoje Niksic]

Francisco Solsona <solsona@deprof.fciencias.unam.mx> writes:

> Comparison between integer and character is constant nil (-1 and ?0)

The warning is totally bogus.  You should turn off debugging code in
your XEmacs.