Peter Memishian wrote:
> The documentation (design doc) quite clearly states how/why these
> events are generated and all good programmers read documentation in
> order to not be confused, right?
By that argument, we might as well name the constant NE_XYZZY. Obviously,
the intent is also to describe the event. My view is that a good event
description should include both the name of the object and the event
occurring on it; thus NE_ADDRESS_CHANGE (or NE_ADDR_CHANGE) is good.
Ok, so you've thrown up one name, NE_ILL_*, which I don't
beieve is a good choice, do you have any other suggestions
on how to better qualify the UP/DOWN event names?
Darren
_______________________________________________
networking-discuss mailing list
[email protected]
