DIP33: A standard exception hierarchy
Dmitry Olshansky
dmitry.olsh at gmail.com
Tue Apr 2 09:53:34 PDT 2013
02-Apr-2013 20:39, H. S. Teoh пишет:
> On Tue, Apr 02, 2013 at 05:47:30PM +0200, Lars T. Kyllingstad wrote:
> [...]
>> I have thought some more about it, and a basic serial comms error
>> should probably be an IOException. An error in a higher-level serial
>> protocol, on the other hand, would be a NetworkException, and then the
>> name doesn't suck so much. CommException may still be better though,
>> or maybe ProtocolException.
> [...]
>
> ProtocolException sounds like a low-level TCP or IP exception. I think
> NetworkException is still the best name, not overly specific, not overly
> generic. CommException sounds a bit too vague to me.
>
Yeah, I've come to conclusion that NetworkException beats CommException
in 90% of cases. The rest 10% can leave with Network being a sane name.
--
Dmitry Olshansky
More information about the Digitalmars-d
mailing list