Re: [nimh-dev] exceptions

["Jon Stewart" <stew1@xxxxxxxxxxx>]

> Having only the one exception in mhlib is already becoming a nuisance in 
> trying to extend it. It's awkward to trap for different errors when they're 
> all of type Error and the only thing that differentiates them is their 
> associated text.
> 
> I think I'm going to start adding some error classes, like 
> BadMessageListError and EmptySequenceError.


I agree with this. Checking type information is a far better practice than 
checking text.


Jon
-- 
Jon Stewart                                 Advanced Los Angeles C++
stew1@xxxxxxxxxxx                           http://www.alacpp.org
_______________________________________________
nimh-dev mailing list
nimh-dev@xxxxxxxxxxx
http://lists.ellipsis.cx/mailman/listinfo/nimh-dev