CERROR, and the ubiquitous "Unclaimed Message" error

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

    Date: 7 December 1980 07:21-EST
    From: Jon L White <JONL at MIT-MC>
    To:   BUG-LISP at MIT-MC
    cc:   GJC at MIT-MC
    Re:   CERROR, and the ubiquitous "Unclaimed Message" error

    How often do you get in to a loop trying to print out the
    object which didn't claim a message?  infinitely often, for
    often an object which doesn't claim some random <foo> msg
    will also fail to claim the PRINT msg.  So for now, I'm making
    it just print the address of the offender.  If the loser wants,
    he can just MUNKAM that address.

This should never happen.  OBJECT-CLASS has a PRINT method, and every
instantiated class should be an inferior of OBJECT-CLASS.  So if this would
indeed happen, it should be reported as a separate problem.  I'd make
the unclaimed message handler check to see if the message being complained
about is the PRINT message, and handle it specially.  What think you?