STRING-MISMATCHQ does NOT work.

[Richard Mark Soley <SOLEY at MIT-MC>]

	********** BUG REPORT **********

Why WHY WHY was STRING-MISMATCHQ changed?  It was working so well....
STRING-MISMATCHQ should return a FIXNUM (index of first change)
or it should return NIL (no difference in strings).  The current
string-mismatchq returns NIL or #T (incorrectly, I might add), all
of which adds up to NILE being dead in the water yet again.

I believe it is the VERY VERY INCORRECT REPEAT INCORRECT call to
str/:compare-words inside a #+PDP-10 in STRING-MISMATCHQ in 
NILCOM;STRING >; remember that str/:compare-words, to be fast, does
NOT bother to return WHERE discrepancies arise, it just returns
if they DO OR NOT.

It would be very nice if this BUG was fixed sometime in the
not-too-distant future.

        ********** BUG REPORT **********

		-- Richard