Wes> By your definition, you should have no issues if Wes> I used the TruthValue TC and in the text clause reversed the meaning Wes> of the true/false values (extreme example, of course)
I don't think that's a fair comparison. You're talking about changing the semantics of the TC completely. Using a RowStatus column to indicate the operational state of a row may well be frowned on, but does still correspond to the basic descriptions of these values. (Though I'll accept that specifying an infinite timeout is probably stretching the spirit of things a bit!) Wes> Considering how hard it is interpret the RowStatus TC as it is I'm not sure it is necessarily that hard - certainly not if you take the basic definition as the first page (everything up to "NOTE WELL"), and regard everything that follows as expanding on this. If anything, I think the flaws in this definition are due to it trying to be too comprehensive and prescriptive. That's where inconsistencies (such as the handling of sparse tables) creep in. Wes> do you really think overloading it for another use is wise? But it doesn't really feel like "another" use - it feels the natural way to use this syntax. If it wasn't for all this extra guff, we'd have a perfectly serviceable three-way operational status object, that could also be used to create and delete rows. But it's clear that the general concensus is against me on this one, and since the rest of you are meant to be concentrating on supporting the new 5.2 release, I'll concede gracefully. (Now I just need to consider the implications for the book :-( ) Dave ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Net-snmp-coders mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
