SYMBOLCONC, STRINGs, and other things being D.E.A.D.

[Robert W. Kerns <RWK at MIT-MC>]

    Date: 6 December 1980 06:22-EST
    From: Jon L White <JONL at MIT-MC>
    Subject: SYMBOLCONC, STRINGs, and other things being D.E.A.D.
    To: KMP at MIT-MC
    cc: BUG-LISP at MIT-MC, RWK at MIT-MC

    Re:
        Date: 5 December 1980 16:49-EST
        From: Kent M. Pitman <KMP at MIT-MC>
	In Maclisp, with STRING loaded, (SYMBOLCONC "FOO" "BAR") gives a
	circular .  .  .
    This is entirely and wholly due to a buggy SENDI file installed by RWK
    yesterday at 15:05:46 -- the problem is the failure of the new SENDI to set
    up the variables SI:CLASS-MARKER and *:CLASS-MARKER.  Not only does
    SYMBOLCONC give "bizarre" results, but any use whatsoever of any data
    interfaceing to the CLASS system is effectively dead.

    Fixed in SENDI 97.

    RWK: do a SRCCOM on SENDI to see what I changed -- I believe that the
	 second BOUNDP in the .SXEVAL is the loss.

Well, all I can say is I was lead astray by GJC reporting that it worked (after
previous problems) I guess all he really determined was that it loaded.  Guess
I should do my own testing...  The reason SENDI was installed early was to
enable it to work in both regimes.  Clarification:  Note that the problem is
note exactly the failure of SENDI to set up the variables SI:CLASS-MARKER and
*:CLASS-MARKER.  That is and was the responsibility of EXTEND.  The .SXEVAL is
merely a cross-compatibility hack that failed, sigh.