~<STRING BUG> --> <BROKEN LISP>

[JONL at MIT-MC (Jon L White)]

Yes, your analysis is right -- the two lines
	MOVEI A,STR%AR
	JSP TT,$GCMKAR
are completely bogus and should be removed -- I must have forgotten
that $GCMKAR doesn't check what kind of array it is marking.
As for the need for this array, LISP;NEW RECENT, which is about to
become LISP RECENT, mentions +INTERNAL-CHAR-N, +INTERNAL-RPLACHAR-N,
+INTERNAL-STRING-WORD-N, and +INTERNAL-SET-STRING-WORD-N.  These
are being "built-in" to accommodate both the STRING package and GSB's
private verions of strings;  it's partly the un-interruptibility
question that makes this necessary (verry short functions don't 
even want to push and pop INHIBIT).