Re: Can this callback mechanism be generified?

Lew wrote:
> Daniel Pitts wrote:
>>> It would be more appropriate to throw an IllegalArgumentException I 
>>> think.  It would probably be even more appropriate to throw a 
>>> CallbackException of your own creation.
> 
> Casper Bang wrote:
>> you're right, IllegalArgumentException is more applicable.
> 
> Perversely, RuntimeExceptions are more about programming mistakes and 
> checked exceptions are more about predicted runtime chaos outside the 
> programmer's control.
> 
> This reasoning supports the use of IllegalArgumentException in this 
> scenario.  The programmer might not be able to stop 'new FileReader( f 
> )' from throwing a FileNotFoundException, but they sure ought to 
> forestall an illegal argument.
> 
Wait, did we all just agree or not? I'm a little confused because it 
seems like Lew is countering the suggestion, but appears to come to the 
same conclusion...

Or were you countering my suggestion to throw a custom 
CallbackException?  In this particular circumstance, I agree with you. I 
was thinking of something else when I suggested CallbackException :-)

-- 
Daniel Pitts' Tech Blog: <http://virtualinfinity.net/wordpress/>