Would it be such a sin for an instantiated protoObject to respond to 
a message (like printString) by sending an exception (Perhaps a 
ProtoException just for that purpose to emphasize the seriousness of 
the error) rather than incurring the wrath of the infinite loop?  I 
understand this is a "behavior" by a behaviorless object, but so, 
too, is a systemic abort!

Dividing by zero is "undefined" in theory, but throws an error in 
practice, why not "ProtoObject new printString."