dblack / candle.superlink.net wrote:
> I've actually been thinking about whether one could plausibly
> implement a sort of "NACK" response (i.e., lack of response) from an
> object, which would be neither nil nor false nor an exception, but
> which would happen in the course of the method being called:

A quick hack would be to have a NackClass, mix in Singleton, and have a
global variable $nack pointing to the instance. Then have a
method_missing returning $nack for every class you want to exhibit the
behaviour.

Now if only method_missing called super by default we could just have
this as a mixin to object. Though it would still conflict with any other
Object#method_missing anyone wanted to write. 

martin